[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGS+omCDxj_wMDiAiywSv4hAtq6E9vm+CxgG8gs1TmrrS499mQ@mail.gmail.com>
Date: Mon, 21 Dec 2015 14:51:14 +0800
From: Daniel Kurtz <djkurtz@...omium.org>
To: Yingjoe Chen <yingjoe.chen@...iatek.com>
Cc: Fabio Estevam <fabio.estevam@...escale.com>,
Maoguang Meng <maoguang.meng@...iatek.com>,
Axel Lin <axel.lin@...ics.com>,
Hongzhou Yang <hongzhou.yang@...iatek.com>,
Linus Walleij <linus.walleij@...aro.org>,
Patrice Chotard <patrice.chotard@...com>,
open list <linux-kernel@...r.kernel.org>,
Fabian Frederick <fabf@...net.be>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] pinctrl: mediatek: convert to arch_initcall
On Fri, Dec 18, 2015 at 11:06 PM, Yingjoe Chen
<yingjoe.chen@...iatek.com> wrote:
> On Fri, 2015-12-18 at 12:21 +0800, Daniel Kurtz 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>
>> ---
>> drivers/pinctrl/mediatek/pinctrl-mt6397.c | 2 +-
>> drivers/pinctrl/mediatek/pinctrl-mt8127.c | 2 +-
>> drivers/pinctrl/mediatek/pinctrl-mt8135.c | 2 +-
>> drivers/pinctrl/mediatek/pinctrl-mt8173.c | 2 +-
>> 4 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/pinctrl/mediatek/pinctrl-mt6397.c b/drivers/pinctrl/mediatek/pinctrl-mt6397.c
>> index f9751ae..a3780d4 100644
>> --- a/drivers/pinctrl/mediatek/pinctrl-mt6397.c
>> +++ b/drivers/pinctrl/mediatek/pinctrl-mt6397.c
>> @@ -70,7 +70,7 @@ static int __init mtk_pinctrl_init(void)
>> return platform_driver_register(&mtk_pinctrl_driver);
>> }
>>
>> -module_init(mtk_pinctrl_init);
>> +arch_initcall(mtk_pinctrl_init);
>
>
> MT6397 is PMIC, which depends on pwrap on main AP to work. Since
> pmic-wrap itself is module_platform_driver, I think it make sense to
> keep this one as module_init. Maybe adding a comment to explain why it
> is different from others will help.
I interpret this the other way - I think that since the PMIC wrapper
provides a bus required for the system PMIC it should also be a
builtin and use arch_initcall.
WDYT?
-Dan
--
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