From: Fabio Porcedda Date: Tue, 26 Mar 2013 09:35:15 +0000 (+0100) Subject: driver core: warn that platform_driver_probe can not use deferred probing X-Git-Tag: v3.10-rc1~193^2~15 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=647c86d0a2d1131dd9412361958d8e0aae949523;p=platform%2Fupstream%2Fkernel-adaptation-pc.git driver core: warn that platform_driver_probe can not use deferred probing Add documentation that platform_driver_probe() is incompatible with deferred probing. Signed-off-by: Fabio Porcedda Cc: Arnd Bergmann Cc: Geert Uytterhoeven Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/base/platform.c b/drivers/base/platform.c index c0b8df3..ef2afb1 100644 --- a/drivers/base/platform.c +++ b/drivers/base/platform.c @@ -555,7 +555,8 @@ EXPORT_SYMBOL_GPL(platform_driver_unregister); /** * platform_driver_probe - register driver for non-hotpluggable device * @drv: platform driver structure - * @probe: the driver probe routine, probably from an __init section + * @probe: the driver probe routine, probably from an __init section, + * must not return -EPROBE_DEFER. * * Use this instead of platform_driver_register() when you know the device * is not hotpluggable and has already been registered, and you want to @@ -566,6 +567,9 @@ EXPORT_SYMBOL_GPL(platform_driver_unregister); * into system-on-chip processors, where the controller devices have been * configured as part of board setup. * + * This is incompatible with deferred probing so probe() must not + * return -EPROBE_DEFER. + * * Returns zero if the driver registered and bound to a device, else returns * a negative error code and with the driver not registered. */