linux-kernel - Re: Any news on Runtime Interpreted Power Sequences

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131028235344.GB16686@sirena.org.uk>
Date:	Mon, 28 Oct 2013 16:53:44 -0700
From:	Mark Brown <broonie@...nel.org>
To:	NeilBrown <neilb@...e.de>
Cc:	Alex Courbot <acourbot@...dia.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Thierry Reding <thierry.reding@...onic-design.de>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: Re: Any news on Runtime Interpreted Power Sequences

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?

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)