mirror of
https://github.com/torvalds/linux.git
synced 2024-12-26 04:42:12 +00:00
4fc4b274f9
This went unnoticed in durin the merge window:
The dsps driver creates a child device for the musb core driver _and_
attaches the of_node to it so devm_usb_get_phy_by_phandle() grabs the
correct phy and attaches the devm resources to the proper device. We
could also use the parent device but then devm would attach the
resource to the wrong device and it would be destroyed once the parent
device is gone - not the device that is used by the musb core driver.
If the phy is now not available then dsps_musb_init() /
devm_usb_get_phy_by_phandle() returns with EPROBE_DEFER. Since the
of_node is attached it tries OF drivers as well and matches the driver
against DSPS. That one creates a new child device for the musb core
driver which gets probed immediately.
The whole thing repeats itself until the stack overflows.
I belive the same problem exists in ux500 glue code (since
|
||
|---|---|---|
| .. | ||
| am35x.c | ||
| blackfin.c | ||
| blackfin.h | ||
| cppi_dma.c | ||
| cppi_dma.h | ||
| da8xx.c | ||
| davinci.c | ||
| davinci.h | ||
| Kconfig | ||
| Makefile | ||
| musb_am335x.c | ||
| musb_core.c | ||
| musb_core.h | ||
| musb_cppi41.c | ||
| musb_debug.h | ||
| musb_debugfs.c | ||
| musb_dma.h | ||
| musb_dsps.c | ||
| musb_gadget_ep0.c | ||
| musb_gadget.c | ||
| musb_gadget.h | ||
| musb_host.c | ||
| musb_host.h | ||
| musb_io.h | ||
| musb_regs.h | ||
| musb_virthub.c | ||
| musbhsdma.c | ||
| musbhsdma.h | ||
| omap2430.c | ||
| omap2430.h | ||
| tusb6010_omap.c | ||
| tusb6010.c | ||
| tusb6010.h | ||
| ux500_dma.c | ||
| ux500.c | ||