From: Mark Brown <broonie@kernel.org>
To: NeilBrown <neilb@suse.de>
Cc: Alex Courbot <acourbot@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@avionic-design.de>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Any news on Runtime Interpreted Power Sequences
Date: Tue, 29 Oct 2013 09:18:16 -0700 [thread overview]
Message-ID: <20131029161816.GE16686@sirena.org.uk> (raw)
In-Reply-To: <20131029111037.6e59499d@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Tue, Oct 29, 2013 at 11:10:37AM +1100, NeilBrown wrote:
> Yes, the device is soldered down and has a reset line that needs to be pulsed
> low at about the same time that the MMC port enables the regulator.
> How do you propose that I describe this? Which driver should know about the
> reset GPIO, how to I tell it about the GPIO, and which function should do the
> pulsing?
I'd expect the driver for the device to know about this, obviously
depending on what this actually does it might want to use this at
runtime (for example, putting the device into reset to minimise power
while it's idle). We really need a generic way for devices such as this
on enumerable buses to run before the current probe() in order to allow
them to manage their power up sequences in embedded systems, this is
*far* from a unique situation.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-29 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 0:22 NeilBrown
2013-10-25 6:23 ` Alex Courbot
2013-10-25 7:33 ` NeilBrown
2013-10-28 10:01 ` Alex Courbot
2013-10-28 11:10 ` NeilBrown
2013-10-28 23:53 ` Mark Brown
2013-10-29 0:10 ` NeilBrown
2013-10-29 16:18 ` Mark Brown [this message]
2013-10-31 4:59 ` NeilBrown
2013-10-31 5:23 ` Alex Courbot
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=20131029161816.GE16686@sirena.org.uk \
--to=broonie@kernel.org \
--cc=acourbot@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=neilb@suse.de \
--cc=thierry.reding@avionic-design.de \
/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
Powered by JetHome