From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Kozlowski Subject: Re: [PATCH 1/2] power: act8945a: add charger driver for ACT8945A Date: Fri, 08 Jan 2016 16:02:45 +0900 Message-ID: <568F5F15.8050602@samsung.com> References: <1452219225-10510-1-git-send-email-wenyou.yang@atmel.com> <1452219225-10510-2-git-send-email-wenyou.yang@atmel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mailout3.w1.samsung.com ([210.118.77.13]:27922 "EHLO mailout3.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751213AbcAHHCw (ORCPT ); Fri, 8 Jan 2016 02:02:52 -0500 In-reply-to: Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: "Yang, Wenyou" Cc: Sebastian Reichel , Dmitry Eremin-Solenikov , David Woodhouse , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , "Ferre, Nicolas" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-pm@vger.kernel.org" On 08.01.2016 15:43, Yang, Wenyou wrote: [...] >>> +static struct platform_driver act8945a_charger_driver = { >>> + .driver = { >>> + .name = "act8945a-charger", >>> + }, >>> + .probe = act8945a_charger_probe, >>> + .remove = act8945a_charger_remove, }; >>> + >>> +static int __init act8945a_charger_init(void) { >>> + return platform_driver_register(&act8945a_charger_driver); >>> +} >>> +subsys_initcall(act8945a_charger_init); >> >> Why subsys_initcall? This should be regular module_platform_driver. > > I want it to register early enough as MFD. Maybe I am wrong. No, you shouldn't manually order the probing by initcalls. This should be registered as usual and, if needed, support deferred probing. In this case I even can't find any reason to register it earlier than usual. Best regards, Krzysztof From mboxrd@z Thu Jan 1 00:00:00 1970 From: k.kozlowski@samsung.com (Krzysztof Kozlowski) Date: Fri, 08 Jan 2016 16:02:45 +0900 Subject: [PATCH 1/2] power: act8945a: add charger driver for ACT8945A In-Reply-To: References: <1452219225-10510-1-git-send-email-wenyou.yang@atmel.com> <1452219225-10510-2-git-send-email-wenyou.yang@atmel.com> Message-ID: <568F5F15.8050602@samsung.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 08.01.2016 15:43, Yang, Wenyou wrote: [...] >>> +static struct platform_driver act8945a_charger_driver = { >>> + .driver = { >>> + .name = "act8945a-charger", >>> + }, >>> + .probe = act8945a_charger_probe, >>> + .remove = act8945a_charger_remove, }; >>> + >>> +static int __init act8945a_charger_init(void) { >>> + return platform_driver_register(&act8945a_charger_driver); >>> +} >>> +subsys_initcall(act8945a_charger_init); >> >> Why subsys_initcall? This should be regular module_platform_driver. > > I want it to register early enough as MFD. Maybe I am wrong. No, you shouldn't manually order the probing by initcalls. This should be registered as usual and, if needed, support deferred probing. In this case I even can't find any reason to register it earlier than usual. Best regards, Krzysztof