Re: [RESEND PATCH] mfd: sec: initialize driver via module_platform_driver

2021-03-16 Thread Lee Jones
On Tue, 16 Mar 2021, Krzysztof Kozlowski wrote: > From: Krzysztof Kozlowski > > The driver was using subsys_initcall() because in old times deferred > probe was not supported everywhere and specific ordering was needed. > Since probe deferral works fine and specific ordering is discouraged > (hi

[RESEND PATCH] mfd: sec: initialize driver via module_platform_driver

2021-03-16 Thread Krzysztof Kozlowski
From: Krzysztof Kozlowski The driver was using subsys_initcall() because in old times deferred probe was not supported everywhere and specific ordering was needed. Since probe deferral works fine and specific ordering is discouraged (hides dependencies between drivers and couples their boot order

[RESEND PATCH] mfd: sec: initialize driver via module_platform_driver

2020-10-28 Thread Krzysztof Kozlowski
The driver was using subsys_initcall() because in old times deferred probe was not supported everywhere and specific ordering was needed. Since probe deferral works fine and specific ordering is discouraged (hides dependencies between drivers and couples their boot order), the driver can be convert

Re: [PATCH] mfd: sec: initialize driver via module_platform_driver

2020-09-22 Thread Marek Szyprowski
Hi Krzysztof, On 21.09.2020 22:34, Krzysztof Kozlowski wrote: > The driver was using subsys_initcall() because in old times deferred > probe was not supported everywhere and specific ordering was needed. > Since probe deferral works fine and specific ordering is discouraged > (hides dependencies b

[PATCH] mfd: sec: initialize driver via module_platform_driver

2020-09-21 Thread Krzysztof Kozlowski
The driver was using subsys_initcall() because in old times deferred probe was not supported everywhere and specific ordering was needed. Since probe deferral works fine and specific ordering is discouraged (hides dependencies between drivers and couples their boot order), the driver can be convert