[PATCH 3/4] pinctrl: single: omap: Add SoC specific module for wake-up events
From: tony@atomide.com (Tony Lindgren)
Date: 2013-06-12 13:33:06
Also in:
linux-devicetree, linux-omap
From: tony@atomide.com (Tony Lindgren)
Date: 2013-06-12 13:33:06
Also in:
linux-devicetree, linux-omap
* Roger Quadros [off-list ref] [130611 05:57]:
On 06/10/2013 06:21 PM, Tony Lindgren wrote:quoted
* Quadros, Roger [off-list ref] [130610 03:09]:quoted
+ +static int __init pcs_omap_init(void) +{ + platform_driver_register(&pcs_omap_soc_driver); + platform_driver_register(&pcs_omap_driver); + + return 0; +} +module_init(pcs_omap_init); It seems this has to be moved to an earlier place (e.g. subsys_initcall) else the pinctrl core fails to find the pinctrl device at the device creation time and bails out with -EPROBE_DEFER. Also, that device is never created again, so -EPROBE_DEFER doesn't seem to work there.Ah here, found your other comment :) That's not needed, the real fix is to make twl-core.c and friends to be regular module_init. There are already patches queued for that.OK. I was testing with USB host driver and it seems to be loaded as fs_initcall() which is the root of the problem. I will fix up the usb host driver to be loaded as module_init()
OK good to hear. Regards, Tony