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, 24 Apr 2014 09:18:22 -0500
From:	Nishanth Menon <nm@...com>
To:	Mark Brown <broonie@...nel.org>
CC:	<linux-omap@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>,
	Saravana Kannan <skannan@...eaurora.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Markus Pargmann <mpa@...gutronix.de>
Subject: Re: [RESEND PATCH] regulator: core: Disable unused regulators after
 deferred probing is done

On 04/24/2014 08:34 AM, Mark Brown wrote:
> On Wed, Apr 23, 2014 at 06:10:50PM -0500, Nishanth Menon wrote:
>> From: Saravana Kannan <skannan@...eaurora.org>
>>
>> regulator_init_complete does a scan of regulators which dont have
>> always-on or consumers are automatically disabled as being unused.
>> However, with deferred probing, late_initcall() is too soon to
>> declare a regulator as unused as the regulator itself might not
>> have registered due to defferal - Example: A regulator deffered due
>> to i2bus not available which in turn is deffered due to pinctrl
>> availability.
>>
>> Since deferred probing is done in late_initcall(), do the cleanup of
>> unused regulators by regulator_init_complete in late_initcall_sync
>> instead of late_initcall.
> 
> I'll apply this however since as we discussed on IRC last night it's
> going to make the issues with unconfigured regulators getting powered
> off more severe before I do so I'll change things so that regulators
> with no configuration at all don't get touched by the core.
> 
Thanks Mark.

-- 
Regards,
Nishanth Menon
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ