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] [day] [month] [year] [list]

Date:	Thu, 26 Apr 2012 14:40:48 +0530
From:	Jassi Brar <jaswinder.singh@...aro.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Ulf Hansson <ulf.hansson@...ricsson.com>,
	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 26 April 2012 14:05, Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:
> On Wed, Apr 25, 2012 at 09:04:01PM +0530, Jassi Brar wrote:
>
>>  Shouldn't the bootloader be responsible for ensuring MMC is
>> put down after using it and before passing control to the kernel.
>
> You might want to try to ensure that bootloaders always do the right
> thing but I prefer to work on more achievable goals like world peace. :/
>
>From what Ulf described so far, I am not sure if even gagging the regulator
api could be seen as a foolproof solution to the problem - he still doesn't
account for the necessary 'power-down sequence of commands' without
which the eMMC might fail attempts by the mmc stack to reset and initialize.

Appeasements and treaties could help achieve peace, I am just not sure
if former is a good option this time :)
--
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/