From: NeilBrown <neilb@suse.de>
To: Mark Brown <broonie@kernel.org>
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 11:10:37 +1100 [thread overview]
Message-ID: <20131029111037.6e59499d@notabene.brown> (raw)
In-Reply-To: <20131028235344.GB16686@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
On Mon, 28 Oct 2013 16:53:44 -0700 Mark Brown <broonie@kernel.org> wrote:
> On Mon, Oct 28, 2013 at 10:10:04PM +1100, NeilBrown wrote:
>
> > I agree that this power-up sequence should be a property of the device.
> > However until the device has been powered up, Linux doesn't know about it.
> > Neither a board file or a devicetree can (as far as I can tell), tell the
> > MMC port that a particular card is attached. Rather the host probes the card
> > to see what it is.
> > So there isn't any way for the device driver to get control at the
> > appropriate time to effect the proper sequencing.
>
> If it is a genuinely pluggable MMC slot then I'd expect the sequence to
> be implementing whatever is required for standard MMC enumeration to
> work. If the device is a soldered down one with extra control (as is
> quite common) then there shouldn't be a problem describing it?
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?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-10-29 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131025112224.6e5265e6@notabene.brown>
[not found] ` <526A0E71.100@nvidia.com>
[not found] ` <20131025183345.2b963e13@notabene.brown>
2013-10-28 10:01 ` Any news on Runtime Interpreted Power Sequences Alex Courbot
2013-10-28 11:10 ` NeilBrown
2013-10-28 23:53 ` Mark Brown
2013-10-29 0:10 ` NeilBrown [this message]
2013-10-29 16:18 ` Mark Brown
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=20131029111037.6e59499d@notabene.brown \
--to=neilb@suse.de \
--cc=acourbot@nvidia.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).