Thread (37 messages) 37 messages, 6 authors, 2013-08-09

[PATCH v2 1/3] hwmon: (lm90) Add power control

From: linux@roeck-us.net (Guenter Roeck)
Date: 2013-08-08 20:00:22
Also in: linux-tegra, lkml

On Thu, Aug 08, 2013 at 06:15:54PM +0100, Mark Brown wrote:
On Thu, Aug 08, 2013 at 08:21:48AM -0700, Guenter Roeck wrote:
quoted
On 08/08/2013 06:08 AM, Mark Brown wrote:
quoted
quoted
I'd be most surprised if the device worked without power, if the driver
fails to get and enable a regulator for it then that's not great
(especially if it does so silently).
quoted
Correct, but it appears that the driver magically worked for a long time
without it.
Sure, it'll work in systems that have always on regulators.
quoted
Is it guaranteed that the driver keeps working for all cases where
regulator support is enabled in the kernel, and where it used to work
so far without mandating the existence of this specific regulator ?
My main concern is having to deal with complaints that the driver stopped
working for no good reason.
Sure, that's the transition issues I mentioned - the regulator API does
have stubbing facilities which should cover things and it's very easy to
define stub regulators if you need to.  Like I say I expect this to be a
lot easier after the next merge window as another way of doing stubs is
being added which should make this even easier by avoiding disrupting
drivers that do genuinely want to check for absent supplies and handle
that better.
We will need to make sure that all dts files using any of the compatible chips
are updated accordingly. There are several entries in various dts files for
adm1032, adt7461, lm90, and nct1008.
quoted
In this context, is it common practice to name such regulators "vdd"
or similar ? What if there are multiple LM90 or compatible chips
in a system, connected to different power rails ? Who determines
if the regulator is supposed to be named "vdd" or "vcc" or anything
else, and to which power rails it is actually connected ? How can
and does one guarantee that "vdd" is the correct regulator to use
for all systems ? What if some other driver requests "vdd", but the chip
it supports happens to be connected to a different power rail ?
That's not what the name means - they are nothing to do with the board.
Ok, makes sense.
The names requested by a driver are defined with regard to the device
and should be the names used by the chip itself as defined in the
9 votes for vdd, 11 votes for vcc, one undecided (no datasheet available).
Guess one is as good as the other ;-).

Guenter
datasheet.  A board that uses regulators then maps these onto specific
regulators in the system, the driver doesn't need to know anything about
this process.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help