Re: [PATCH] regulator: mt6397: convert to arch_initcall

From	Mark Brown <broonie@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH] regulator: mt6397: convert to arch_initcall
Date	2016-01-05 14:50 +0100
Message-ID	<qNA9Q-3si-3@gated-at.bofh.it> (permalink)
References	<qIOGu-8jX-3@gated-at.bofh.it> <qIQoV-Yy-9@gated-at.bofh.it> <qJ9hU-4kG-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Thu, Dec 24, 2015 at 04:10:43PM +0800, Yingjoe Chen wrote:

> These changes are related to pinctrl init order patch. The related
> discussion is here:
> http://lists.infradead.org/pipermail/linux-mediatek/2015-December/003298.html

So this is just to cut down on probe deferrals?  Sorry but as you'll see
from the discussion in that thread I'm really not enthusiastic about
taking such patches.  Trying to use initcall ordering is a hack we're
moving towards removing, isn't very robust and makes it harder to
convince people that it's worth doing anything to really improve things.

> I think Henry use arch_initcall because that's what pinctrl patch was
> using. In this case, we should use subsys_initcall for all these.

But why?  This sort of random unexplained level picking is part of the
problem...

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

Thread

Re: [PATCH] regulator: mt6397: convert to arch_initcall Mark Brown <broonie@kernel.org> - 2016-01-05 14:50 +0100

csiph-web