From: Wei Ni <wni@nvidia.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: Guenter Roeck <linux@roeck-us.net>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Matthew Longnecker <MLongnecker@nvidia.com>,
"khali@linux-fr.org" <khali@linux-fr.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] hwmon: (lm90) Add power control
Date: Wed, 7 Aug 2013 17:35:05 +0800 [thread overview]
Message-ID: <520214C9.1010200@nvidia.com> (raw)
In-Reply-To: <1375865105.562600640@f434.i.mail.ru>
On 08/07/2013 04:45 PM, Alexander Shiyan wrote:
>> On 08/07/2013 03:50 PM, Guenter Roeck wrote:
>>> On 08/07/2013 12:32 AM, Wei Ni wrote:
>>>> On 08/07/2013 03:27 PM, Alexander Shiyan wrote:
>>>>>> The device lm90 can be controlled by the vdd rail.
>>>>>> Adding the power control support to power on/off the vdd rail.
>>>>>> And make sure that power is enabled before accessing the device.
>>>>>>
>>>>>> Signed-off-by: Wei Ni <wni@nvidia.com>
>>>>>> ---
>>>>>> drivers/hwmon/lm90.c | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> [...]
>>>>>> + if (!data->lm90_reg) {
>>>>>> + data->lm90_reg = regulator_get(&client->dev, "vdd");
>>>>>> + if (IS_ERR_OR_NULL(data->lm90_reg)) {
>>>>>> + if (PTR_ERR(data->lm90_reg) == -ENODEV)
>>>>>> + dev_info(&client->dev,
>>>>>> + "No regulator found for vdd. Assuming vdd is always powered.");
>>>>>> + else
>>>>>> + dev_warn(&client->dev,
>>>>>> + "Error [%ld] in getting the regulator handle for vdd.\n",
>>>>>> + PTR_ERR(data->lm90_reg));
>>>>>> + data->lm90_reg = NULL;
>>>>>> + mutex_unlock(&data->update_lock);
>>>>>> + return -ENODEV;
>>>>>> + }
>>>>>> + }
>>>>>> + if (is_enable) {
>>>>>> + ret = regulator_enable(data->lm90_reg);
>>>>>> + msleep(POWER_ON_DELAY);
>>>>>
>>>>> Can this delay be handled directly from regulator?
>>>>
>>>> I think it should be handled in the device driver.
>>>> Because there have different delay time to wait devices stable.
>>>>
>>>
>>> Then why does no other caller of regulator_enable() need this ?
>>> I don't think lm90 is so much different to other users of regulator
>>> functionality.
>>
>> May be I'm wrong. I noticed that in lm90 SPEC, the max of "SMBus Clock
>> Low Time" is 25ms, so I supposed that it may need about 20ms to stable
>> after power on.
>>
>> Anyway, if I remove this delay, the driver also works fine, so I will
>> remove it in my next patch.
>
> I originally had in mind that regulator API contain own delay option.
> E.g. reg-fixed-voltage && gpio-regulator contains "startup-delay-us" property.
As I know the "startup-delay-us" is used for the regulator device, not
the consumer devices.
In this patch, msleep(POWER_ON_DELAY) was used to wait the lm90 stable,
but it seems it's unnecessary now :)
Wei.
>
> ---
>
next prev parent reply other threads:[~2013-08-07 9:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 6:52 [PATCH 0/2] Add power control for lm90 Wei Ni
2013-08-07 6:52 ` [PATCH 1/2] hwmon: (lm90) Add power control Wei Ni
2013-08-07 7:03 ` Guenter Roeck
2013-08-07 7:15 ` Wei Ni
2013-08-07 7:27 ` Alexander Shiyan
2013-08-07 7:32 ` Wei Ni
2013-08-07 7:50 ` Guenter Roeck
2013-08-07 8:07 ` Wei Ni
2013-08-07 8:45 ` Alexander Shiyan
2013-08-07 9:35 ` Wei Ni [this message]
2013-08-07 16:06 ` Stephen Warren
2013-08-07 16:44 ` Guenter Roeck
2013-08-07 7:45 ` Guenter Roeck
2013-08-07 6:52 ` [PATCH 2/2] ARM: dt: t114 dalmore: add dt entry for nct1008 Wei Ni
2013-08-07 16:03 ` Stephen Warren
2013-08-08 2:36 ` Wei Ni
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=520214C9.1010200@nvidia.com \
--to=wni@nvidia.com \
--cc=MLongnecker@nvidia.com \
--cc=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=shc_work@mail.ru \
--cc=swarren@wwwdotorg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).