Re: [PATCH v3 01/18] platform: delay OF device-driver matches until late_initcall
From: Tomeu Vizoso <hidden>
Date: 2015-09-04 05:46:46
Also in:
linux-acpi, linux-arm-kernel, lkml
From: Tomeu Vizoso <hidden>
Date: 2015-09-04 05:46:46
Also in:
linux-acpi, linux-arm-kernel, lkml
On 10 August 2015 at 12:25, Mark Brown [off-list ref] wrote:
On Sun, Aug 09, 2015 at 03:03:14PM +0200, Tomeu Vizoso wrote:quoted
There was some recent thread about how the disabling of unused clocks and regulators isn't really safe because after late_initcall_sync more drivers can be registered from modules. Furthermore, there's async device probes.What recent thread and why would that be unsafe?
Sorry, I should have said instead that it's already unpredictable and that from what I have seen during testing these series doesn't make it any worst. Regards, Tomeu
Any driver using a clock or regulator ought to be making sure that the clock or regulator is enabled before it tries to use it. The worst that should happen is that something gets the power bounced during boot which isn't the end of the world.