linux-kernel - Re: [PATCH] regulator: core: Keep boot

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]

Date:	Tue, 24 Apr 2012 10:09:40 +0200
From:	Ulf Hansson <ulf.hansson@...ricsson.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mattias WALLIN <mattias.wallin@...ricsson.com>,
	Jonas ABERG <jonas.aberg@...ricsson.com>,
	Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH] regulator: core: Keep boot_on regulators powered during
 init

On 04/23/2012 08:01 PM, Mark Brown wrote:
> On Mon, Apr 23, 2012 at 02:45:10PM +0200, Ulf Hansson wrote:
>
>> A typical mmc host driver is when finished it's probe routine,
>> trigger of a so called mmc_rescan work which is taking care of
>> detecting and initializing the eMMC card. It is a quite complicated
>> procedure which preferably not to be handled from the host driver's
>> probe function.
>
>> If the platform already have booted from the eMMC card, the card is
>> already powered an initialized from a bootloader. Cutting the power
>> without first notifying the card by sending commands to it, must be
>> prevented and also violates the eMMC specification. In the end, it
>> will mean that the detect and initialization procedure fails.
>
> Can the driver use is_enabled() in the probe routine to check the
> current status during probe and hand off appropriately?  The issue here
> seems like it's the fact that the driver isn't managing to bootstrapping
> of its state well.

Well, it is not as simple as that. An mmc host driver is just a driver 
for handling a certain mmc IP. Uper layers handles the (e)MMC/SD/SDIO 
protocol including controlling power the card. Moreover the complicated 
detect procedure is handled in a work.

In principle what you are proposing will mean that each mmc host driver 
will have to "flush" the rescan work from probe. This will have horrid 
impact on boot time since rescan can take several hundred of 
milliseconds for each eMMC/SD/SDIO card. Is is far better to handle the 
rescan in parallel works.

I really think it would be much beneficial to be able to tell the late 
init call (regulator_init_completet) to back off from disabling this 
regulator. If not using boot_on, we can invent another regulator 
constraint for this. What do you think of this?

>
> Worst case seems to be that the card will be briefly powered during boot
> then turned off again after enumeration which doesn't seem like the end
> of the world to me.

It is really crucial that the regulator is not switched off in an 
uncontrolled manner. It will mean viloating eMMC spec and in many cases 
the hw is not able to reset the eMMC and thus the detect procedure will 
fail. Likely the eMMC holds root file system then the platform wont boot...

Kind regards
Ulf Hansson
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/