From: Linus Walleij <linus.walleij@linaro.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Bengt Jonsson <bengt.g.jonsson@stericsson.com>
Subject: Re: [PATCH 2/4] regulator: add ab8500 per-regulator startup delay
Date: Thu, 10 Mar 2011 16:43:50 +0100 [thread overview]
Message-ID: <AANLkTim5Qw_PQJ234YsNvvmsg7L-RGfTsuMaTHvUmLHK@mail.gmail.com> (raw)
In-Reply-To: <20110310134953.GE22195@opensource.wolfsonmicro.com>
On Thu, Mar 10, 2011 at 2:49 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Thu, Mar 10, 2011 at 02:43:41PM +0100, Linus Walleij wrote:
>> From: Bengt Jonsson <bengt.g.jonsson@stericsson.com>
>>
>> Since some regulators can take some time to come online, we
>> define a per-regulator millisecond delay value and assign
>> to the slow TV-out regulator.
>
> You should be implementing the enable_time() operation for the regulator
> for this.
I looked into it, but the core implicitly only does delays after
enable(), and our delays affect disable() and set_voltage()
as well. disable() may look superfluous but I bet there may be
cases where not having a voltage fully disabled before doing
something will cause immesurable harm.
I was thinking about extending the present mechanism in
core by refactoring the signature of the enable_time()
as such:
/* Operations that we want to enumerate to the enable_time() call */
enum regulator_op {
REGULATOR_ENABLE,
REGULATOR_DISABLE,
REGULATOR_SET_VOLTAGE,
REGULATOR_SET_MODE,
};
/* Time taken to enable the regulator */
int (*enable_time) (struct regulator_dev *, enum regulator_op op);
Then I'll have to break out the delay code and refactor a bit,
altering the few drivers using it I guess.
Sounds like a plan?
Yours,
Linus Walleij
next prev parent reply other threads:[~2011-03-10 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 13:43 Linus Walleij
2011-03-10 13:49 ` Mark Brown
2011-03-10 15:43 ` Linus Walleij [this message]
2011-03-10 15:53 ` Mark Brown
2011-03-11 11:08 ` Linus Walleij
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=AANLkTim5Qw_PQJ234YsNvvmsg7L-RGfTsuMaTHvUmLHK@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bengt.g.jonsson@stericsson.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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
all inboxes | Powered by JetHome®