From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
Grant Likely <grant.likely@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Hongzhou Yang <hongzhou.yang@mediatek.com>,
Fabio Estevam <fabio.estevam@freescale.com>,
Fabian Frederick <fabf@skynet.be>,
Maoguang Meng <maoguang.meng@mediatek.com>,
Axel Lin <axel.lin@ingics.com>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] pinctrl: mediatek: convert to arch_initcall
Date: Wed, 30 Dec 2015 17:22:12 +0000 [thread overview]
Message-ID: <20151230172212.GZ16023@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdbRDzXunYK5d6Ld4Z2a=0mkp4KBvgL2P-St4P65Jajamw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Tue, Dec 22, 2015 at 04:11:47PM +0100, Linus Walleij wrote:
> On Tue, Dec 22, 2015 at 2:46 PM, Daniel Kurtz <djkurtz@chromium.org> wrote:
> > Move pinctrl initialization earlier in boot so that real devices can find
> > their pctldev without probe deferring.
> (...)
> > -module_init(mtk_pinctrl_init);
> > +arch_initcall(mtk_pinctrl_init);
> So I see why you're doing this (because of wanting to avoid nasty boot
> probe deferrals, right?) and I'm going to apply it, because the work
> with probe ordering is still in the works, but I'd like some general
> ARM people to come in with opinions.
I really don't think we should be applying this sort of stuff unless
things are actively broken right now. It's a bit of a rabbit hole we
could spend a long time going down tweaking things for different
systems in the same way that tweaking the link order can be and it masks
the underlying issues.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-30 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 13:46 [PATCH] pinctrl: mediatek: convert to arch_initcall Daniel Kurtz
2015-12-22 15:11 ` Linus Walleij
2015-12-30 17:22 ` Mark Brown [this message]
2015-12-31 13:45 ` Daniel Kurtz
2015-12-31 22:07 ` Mark Brown
2016-01-01 1:56 ` Daniel Kurtz
2016-01-01 14:27 ` Matthias Brugger
2016-01-01 17:29 ` Linus Walleij
2016-01-04 17:12 ` Mark Brown
2016-01-04 18:23 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2015-12-18 4:21 Daniel Kurtz
2015-12-18 15:06 ` Yingjoe Chen
2015-12-21 6:51 ` Daniel Kurtz
2015-12-21 12:39 ` Yingjoe Chen
2015-12-21 12:45 ` Daniel Kurtz
2015-12-22 10:23 ` Linus Walleij
2015-12-22 13:36 ` Yingjoe Chen
2015-12-22 13:41 ` Daniel Kurtz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151230172212.GZ16023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=axel.lin@ingics.com \
--cc=djkurtz@chromium.org \
--cc=fabf@skynet.be \
--cc=fabio.estevam@freescale.com \
--cc=grant.likely@linaro.org \
--cc=hongzhou.yang@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=yingjoe.chen@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).