[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1450791416.20501.7.camel@mtksdaap41>
Date: Tue, 22 Dec 2015 21:36:56 +0800
From: Yingjoe Chen <yingjoe.chen@...iatek.com>
To: Linus Walleij <linus.walleij@...aro.org>
CC: Daniel Kurtz <djkurtz@...omium.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Fabio Estevam <fabio.estevam@...escale.com>,
Hongzhou Yang <hongzhou.yang@...iatek.com>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@...osoft.com>,
Fabian Frederick <fabf@...net.be>,
Maoguang Meng <maoguang.meng@...iatek.com>,
Axel Lin <axel.lin@...ics.com>,
Patrice Chotard <patrice.chotard@...com>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH] pinctrl: mediatek: convert to arch_initcall
On Tue, 2015-12-22 at 11:23 +0100, Linus Walleij wrote:
> On Fri, Dec 18, 2015 at 5:21 AM, Daniel Kurtz <djkurtz@...omium.org> wrote:
>
> > Move pinctrl initialization earlier in boot so that real devices can find
> > their pctldev without probe deferring.
> >
> > Signed-off-by: Daniel Kurtz <djkurtz@...omium.org>
>
> I interpret the discussion as I should wait for a new version of this?
>
> Or should it be applied?
We'll have another patch to change init orders for pwrap, mt6397 mfd
core and mt6397 regulator. Before that, the mt6397 pinctrl changes in
this patch won't work as expect. Apply this now won't cause any problem
either, unless someone think we should stink to current orders.
So I think we could apply this now:
Acked-by: Yingjoe Chen <yingjoe.chen@...iatek.com>
Joe.C
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists