Re: [PATCH v3 01/18] platform: delay OF device-driver matches until late_initcall

From	Tomeu Vizoso <tomeu.vizoso@collabora.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v3 01/18] platform: delay OF device-driver matches until late_initcall
Date	2015-09-04 07:50 +0200
Message-ID	<q4S2S-1oE-9@gated-at.bofh.it> (permalink)
References	(2 earlier) <pUzNT-2I6-7@gated-at.bofh.it> <pUK6D-N5-37@gated-at.bofh.it> <pUTjA-5Qk-1@gated-at.bofh.it> <pVywq-6Xi-11@gated-at.bofh.it> <pVSv8-3oY-19@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 10 August 2015 at 12:25, Mark Brown <broonie@kernel.org> wrote:
> On Sun, Aug 09, 2015 at 03:03:14PM +0200, Tomeu Vizoso wrote:
>
>> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH v3 01/18] platform: delay OF device-driver matches until late_initcall Tomeu Vizoso <tomeu.vizoso@collabora.com> - 2015-09-04 07:50 +0200

csiph-web