Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1301536 > unrolled thread

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

Started byMark Brown <broonie@kernel.org>
First post2016-01-05 14:50 +0100
Last post2016-01-05 14:50 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#1301536 — Re: [PATCH] regulator: mt6397: convert to arch_initcall

FromMark Brown <broonie@kernel.org>
Date2016-01-05 14:50 +0100
SubjectRe: [PATCH] regulator: mt6397: convert to arch_initcall
Message-ID<qNA9Q-3si-3@gated-at.bofh.it>

[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...

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web