linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Daniel Kurtz <djkurtz@chromium.org>,
	Grant Likely <grant.likely@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Cc: 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: Tue, 22 Dec 2015 16:11:47 +0100	[thread overview]
Message-ID: <CACRpkdbRDzXunYK5d6Ld4Z2a=0mkp4KBvgL2P-St4P65Jajamw@mail.gmail.com> (raw)
In-Reply-To: <1450792017-7120-1-git-send-email-djkurtz@chromium.org>

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.

Yours,
Linus Walleij

  reply	other threads:[~2015-12-22 15:11 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 [this message]
2015-12-30 17:22   ` Mark Brown
2015-12-31 13:45     ` Daniel Kurtz
2015-12-31 22:07       ` Mark Brown
     [not found]         ` <20151231220712.GD16023-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
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
     [not found]   ` <CACRpkdbuL5Kjeqb-zJg9DmoxKzy7vphYgBTG-Ffh2i=UVH97ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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='CACRpkdbRDzXunYK5d6Ld4Z2a=0mkp4KBvgL2P-St4P65Jajamw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=axel.lin@ingics.com \
    --cc=broonie@kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=fabf@skynet.be \
    --cc=fabio.estevam@freescale.com \
    --cc=grant.likely@linaro.org \
    --cc=hongzhou.yang@mediatek.com \
    --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).