From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Grant Likely <grant.likely@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
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: Mon, 4 Jan 2016 17:12:57 +0000 [thread overview]
Message-ID: <20160104171257.GO16023@sirena.org.uk> (raw)
In-Reply-To: <CACRpkdZsQc_Jug1dy-qist4Dv7HTDDx-fBjXTxj+s7W0sgJSuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Fri, Jan 01, 2016 at 06:29:15PM +0100, Linus Walleij wrote:
> On Fri, Jan 1, 2016 at 3:27 PM, Matthias Brugger <matthias.bgg@gmail.com> wrote:
> > I think what Mark means is, that we define some pinctrl_initcall which
> > is a macro to subsys_initcall (or arch_initcall or similar). We apply this
> > to all pinctrl drivers including the one from Mediatek. This way at least
> > we have a common method and changing the behaviour in the future is
> > easier to handle.
> That would be pinctrl_soc_initcall() in that case. Just pinctrl_initcall()
> would assume it's for all drivers and there is a bunch of them that are just
> fine with simple device_initcall()s.
OTOH it might be easier to just have an initcall (or fiddle with the
link order) for everything to avoid having to think about which drivers
things apply to.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-04 17:12 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
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 [this message]
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=20160104171257.GO16023@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