Thread (2 messages) flat view 2 messages, 2 authors, 2014-09-24

Re: regulator node names and unit-addresses? (Re: [PATCH v2 1/5] ARM: shmobile: kzm9d: Remove spurious regulator base addresses)

From: Mark Brown <broonie@kernel.org>
Date: 2014-09-24 08:14:55
Also in: linux-arm-kernel, linux-sh

On Wed, Sep 24, 2014 at 09:02:23AM +0200, Geert Uytterhoeven wrote:
On Wed, Sep 24, 2014 at 3:13 AM, Simon Horman [off-list ref] wrote:
quoted
What should we call the nodes?
"regulator0" and "regulator1"?
"regulator1v8" and "regulator3v3"?
Documentation/devicetree/bindings/regulator/regulator.txt doesn't mention
node names or (presence/lack of) unit-adresses, but the examples do have
unit-addresses.
Is this another case where we don't follow the "no reg, no unit-address"
ePAPR rule?
As far as the regulator API is concerned the node name is completly
immaterial and all this stuff is just verbiage we're forced to include.
As far as I can tell the requirement that node names be in the form
"regulator" or whatever is just another thing that wasn't terribly well
thought through in ePAPR, they were trying to do classes I think.

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help