This change is indended to prevent a situation, when a user finds unworking
musb controller on his board. Due to a restriction of determined order of
musb-{omap2430,da8xx,blackfin,tusb,am35x,ux500,davinci} and musb-hdrc
loading, there is no option to have a working musb controller, if the
correspondent module with a particular controller support is loaded after musb
core.
Note, that all of the touched drivers have subsys_initcall() initialization,
which basically doesn't have any special load order meaning, if a driver is
compiled as module.
Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@xxxxxxxxx>
Cc: Felipe Balbi <balbi@xxxxxx>
---
drivers/usb/musb/Kconfig | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
index 07a0346..6eb446e 100644
--- a/drivers/usb/musb/Kconfig
+++ b/drivers/usb/musb/Kconfig
@@ -36,31 +36,31 @@ choice
depends on USB_MUSB_HDRC
config USB_MUSB_DAVINCI
- tristate "DaVinci"
+ bool "DaVinci"
depends on ARCH_DAVINCI_DMx
config USB_MUSB_DA8XX
- tristate "DA8xx/OMAP-L1x"
+ bool "DA8xx/OMAP-L1x"
depends on ARCH_DAVINCI_DA8XX
config USB_MUSB_TUSB6010
- tristate "TUSB6010"
+ bool "TUSB6010"
depends on ARCH_OMAP
config USB_MUSB_OMAP2PLUS
- tristate "OMAP2430 and onwards"
+ bool "OMAP2430 and onwards"
depends on ARCH_OMAP2PLUS
config USB_MUSB_AM35X
- tristate "AM35x"
+ bool "AM35x"
depends on ARCH_OMAP
config USB_MUSB_BLACKFIN
- tristate "Blackfin"
+ bool "Blackfin"
depends on (BF54x && !BF544) || (BF52x && ! BF522 && !BF523)
config USB_MUSB_UX500
- tristate "U8500 and U5500"
+ bool "U8500 and U5500"
depends on (ARCH_U8500 && AB8500_USB)
endchoice
--
1.7.2.3
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
