Re: [PATCH v3 4/5] regulators: tps65912: Add regulator driver for the TPS65912 PMIC

From: Andrew F. Davis
Date: Tue Sep 29 2015 - 14:59:11 EST

On 09/29/2015 01:38 PM, Mark Brown wrote:
On Tue, Sep 29, 2015 at 01:08:50PM -0500, Andrew F. Davis wrote:
On 09/29/2015 10:13 AM, Mark Brown wrote:

sure that will save me anything as my probe function is called with a DT
match already, so no searching is needed.

You've not understood what that change is replacing, the code I'm
quoting above is exactly that code. Check out some of the existing
drivers using this API.

Looking at other drivers that use this API they all call regulator_register
in a loop in their probe, once for each possible regulator, in this case
letting the API do the DT node search makes sense. My probe on the other-hand
is only called when we already have a DT match, therefor searching is not
necessary and all I have to do is call of_get_regulator_init_data myself on
the already found DT node. No need to add node names to my regulator_desc
and make the API re-search for the node.

Oh, ick. The binding has a compatible string in the individual
regulator bindings which is broken unless there really are lots of
variants being configured via DT (which is just not the case here).
It's not only more typing in the DT,

I don't see this, the alternative is matching to this "regulator-compatible",
why not just use the existing compatible.

it also means that we can't read
back the configuration of the device unless the user goes and creates a
DT which explicitly lists each regulator on the device which is
unhelpful. We should be able to read back the configurations of all the
regulators by simply listing the device in DT.

Could you expand this? I'm not sure I understand why we still cant do this
using this new way.

Bindings should have compatible strings when they describe hardware like this,
we can then do stuff like put the LDO and DCDC drivers in separate modules for
instance, letting DT only load what we need. There are other benefits like
not having to search our own DT binding for data, and we only get probed for
devices in the DT.

This also eliminates the need for MFD_CORE, we just call
of_platform_populate on ourself and DT helpers do the rest. Why hard code
mfd_cell's and do matching when DT does the same thing.

The fact that this is different to the bindings for other regulator
drivers and requires more code ought to have been a big warning sign
here :(

The binding is the same as the new tps65218 driver, different isn't always
a warning sign. And what do you mean "requires more code"? This regulator
driver is smaller than almost any other. DT takes care of everything for
us relating to hardware instantiation like it should.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at