From: linux@roeck-us•net (Guenter Roeck)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/3] hwmon: (lm90) Add power control
Date: Thu, 08 Aug 2013 14:30:10 -0700 [thread overview]
Message-ID: <52040DE2.50201@roeck-us.net> (raw)
In-Reply-To: <20130808211825.GN6427@sirena.org.uk>
On 08/08/2013 02:18 PM, Mark Brown wrote:
> On Thu, Aug 08, 2013 at 01:00:26PM -0700, Guenter Roeck wrote:
>> On Thu, Aug 08, 2013 at 06:15:54PM +0100, Mark Brown wrote:
>
>>> 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.
>
> Yes, and probably also board files as well. Or either just accept
> bisection trouble for now or wait till the better stubbing is in there -
Ah, that is exactly the trouble I wanted to avoid.
> that will mean that for DT systems the core will just assume the supply
> is really there and not fail requests if it's not in the DT.
>
>>> 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 ;-).
>
> What I've suggested before is to use the name from the part for which
> the driver is named. Assuming the vendor doesn't randomly change their
> datasheet (but that causes problems for hardware engineers so tends to
> be avoided).
>
Makes sense.
Guenter
next prev parent reply other threads:[~2013-08-08 21:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 6:56 [PATCH v2 0/3] Add power control for lm90 Wei Ni
2013-08-08 6:56 ` [PATCH v2 1/3] hwmon: (lm90) Add power control Wei Ni
2013-08-08 7:13 ` Alexander Shiyan
2013-08-08 9:26 ` Wei Ni
2013-08-08 8:42 ` Guenter Roeck
2013-08-08 9:47 ` Wei Ni
2013-08-08 9:57 ` Alexander Shiyan
2013-08-08 9:59 ` Wei Ni
2013-08-08 10:07 ` Wei Ni
2013-08-08 11:23 ` Guenter Roeck
2013-08-08 17:33 ` Stephen Warren
2013-08-08 17:59 ` Guenter Roeck
2013-08-08 18:45 ` Stephen Warren
2013-08-08 17:30 ` Stephen Warren
2013-08-08 17:59 ` Guenter Roeck
2013-08-08 19:27 ` Mark Brown
2013-08-08 11:01 ` Mark Brown
2013-08-08 11:25 ` Guenter Roeck
2013-08-08 13:08 ` Mark Brown
2013-08-08 15:21 ` Guenter Roeck
2013-08-08 17:15 ` Mark Brown
2013-08-08 20:00 ` Guenter Roeck
2013-08-08 21:18 ` Mark Brown
2013-08-08 21:30 ` Guenter Roeck [this message]
[not found] ` <1376027820.695103970@f416.i.mail.ru>
2013-08-09 10:27 ` Proposal: I2C device power (Was: hwmon: (lm90) Add power control) Mark Brown
2013-08-09 10:50 ` Alexander Shiyan
2013-08-09 11:09 ` Mark Brown
2013-08-09 7:23 ` [PATCH v2 1/3] hwmon: (lm90) Add power control Wei Ni
2013-08-09 10:56 ` Mark Brown
2013-08-08 6:56 ` [PATCH v2 2/3] ARM: dt: t114 dalmore: add dt entry for nct1008 Wei Ni
2013-08-08 17:35 ` Stephen Warren
2013-08-09 6:06 ` Wei Ni
2013-08-08 20:36 ` Sergei Shtylyov
2013-08-08 20:40 ` Stephen Warren
2013-08-08 21:33 ` Guenter Roeck
2013-08-09 6:16 ` Wei Ni
2013-08-08 6:56 ` [PATCH v2 3/3] Documentation: dt: hwmon: add OF document for lm90 Wei Ni
2013-08-08 17:37 ` Stephen Warren
2013-08-09 6:10 ` Wei Ni
2013-08-09 16:35 ` Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52040DE2.50201@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox