[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHkwnC9nGsdgOTQZ6VpeDyPWXw7tpP+2oHvnLv6LEr1cNdnrsg@mail.gmail.com>
Date: Fri, 15 Mar 2013 12:18:53 +0100
From: Fabio Porcedda <fabio.porcedda@...il.com>
To: Sascha Hauer <s.hauer@...gutronix.de>
Cc: Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-media <linux-media@...r.kernel.org>,
linux-ide <linux-ide@...r.kernel.org>,
lm-sensors <lm-sensors@...sensors.org>,
linux-input <linux-input@...r.kernel.org>,
linux-fbdev <linux-fbdev@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
H Hartley Sweeten <hsweeten@...ionengravers.com>,
Hans-Christian Egtvedt <hans-christian.egtvedt@...el.com>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH 10/10] drivers: misc: use module_platform_driver_probe()
On Thu, Mar 14, 2013 at 3:06 PM, Sascha Hauer <s.hauer@...gutronix.de> wrote:
> On Thu, Mar 14, 2013 at 01:58:05PM +0000, Arnd Bergmann wrote:
>> On Thursday 14 March 2013, Fabio Porcedda wrote:
>> > This patch converts the drivers to use the
>> > module_platform_driver_probe() macro which makes the code smaller and
>> > a bit simpler.
>> >
>> > Signed-off-by: Fabio Porcedda <fabio.porcedda@...il.com>
>> > Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> > Cc: Arnd Bergmann <arnd@...db.de>
>> > ---
>> > drivers/misc/atmel_pwm.c | 12 +-----------
>> > drivers/misc/ep93xx_pwm.c | 13 +------------
>> > 2 files changed, 2 insertions(+), 23 deletions(-)
>>
>> The patch itself seems fine, but there are two issues around it:
>>
>> * The PWM drivers should really get moved to drivers/pwm and converted to the new
>> PWM subsystem. I don't know if Hartley or Hans-Christian have plans to do
>> that already.
>>
>> * Regarding the use of module_platform_driver_probe, I'm a little worried about
>> the interactions with deferred probing. I don't think there are any regressions,
>> but we should probably make people aware that one cannot return -EPROBE_DEFER
>> from a platform_driver_probe function.
The use of module_platform_driver_probe() doesn't change anything about that,
it's exactly the same thing as using "return platform_driver_probe()".
I'm right or I'm missing something? Maybe are you just speaking about
the misuse of "platform_driver_probe"?
Best regards
Fabio Porcedda
>
> I'm worried about this aswell. I think platform_driver_probe shouldn't
> be used anymore. Even if a driver does not explicitly make use of
> -EPROBE_DEFER, it leaks in very quickly if a driver for example uses a
> regulator and just returns the error value from regulator_get.
> Sascha
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
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