From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Juha Keski-Saari <ext-juha.1.keski-saari@nokia.com>
Cc: "lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"dbrownell@users.sourceforge.net"
<dbrownell@users.sourceforge.net>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"De-Schrijver Peter (Nokia-D/Helsinki)"
<Peter.De-Schrijver@nokia.com>,
"Valentin Eduardo (Nokia-D/Helsinki)"
<eduardo.valentin@nokia.com>
Subject: Re: [PATCH 1/1] twl4030-regulator: extend twlreg_info to contain turnon delay and remap
Date: Mon, 14 Dec 2009 11:31:25 +0000 [thread overview]
Message-ID: <20091214113125.GB21066@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1260774317.31691.20.camel@keskisaa-workstation>
On Mon, Dec 14, 2009 at 09:05:17AM +0200, Juha Keski-Saari wrote:
> has been turned on. The DM also quotes a maximum wakeup time for
> returning from sleep to full output, but that delay is much shorter. For
> some regulators the turnon delay is theoretically long enough for the
> reg_enable to return to the driver noticeably earlier than the regulator
> output is actually at target level.
OK. This ramp rate thing is a general issue for regulators, especially
those that are controlled via GPIOs rather than I2C since for them the
control interface takes approximately zero time to respond. Ideally we
want to do something slightly more involved than what you've got here
since if you're turning on more than one regulator at once it'd be nice
to be able to allow all the supplies to ramp in parallel rather than
serialising everything.
I've got a patch half done for this which I should try to finish off and
post soon but for now this should be OK.
prev parent reply other threads:[~2009-12-14 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 7:53 Juha Keski-Saari
2009-12-11 10:35 ` Mark Brown
2009-12-14 7:05 ` Juha Keski-Saari
2009-12-14 11:31 ` Mark Brown [this message]
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=20091214113125.GB21066@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Peter.De-Schrijver@nokia.com \
--cc=dbrownell@users.sourceforge.net \
--cc=eduardo.valentin@nokia.com \
--cc=ext-juha.1.keski-saari@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.com \
/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®