| b30beda2 | 31-Jul-2018 |
Adam Ford <aford173@gmail.com> |
UPSTREAM: usb: musb-new: omap2430: Enable DM_USB and OF support
With upcoming changes that require CONFIG_BLK, this broke USB Mass Storage on the OMAP3 boards because if CONFIG_BLK is enabled, it as
UPSTREAM: usb: musb-new: omap2430: Enable DM_USB and OF support
With upcoming changes that require CONFIG_BLK, this broke USB Mass Storage on the OMAP3 boards because if CONFIG_BLK is enabled, it assumes that DM_USB is enabled, but it wasn't yet available on omap3 and omap4 boards.
This patch converts the OMAP2430 MUSB glue to support DM_USB and extracts the necessary information based on the device tree.
It's based on the ti-musb driver, but there are enough significant differences in both the architecture and device tree entires between am33xx and OMAP3/OMAP4, that I think it makes sense to continue to keep the separate.
Per doc/driver-model/usb-info.txt, the USB gadget stuff hasn't migrated to DM_USB yet, so this only supports USB Host for now.
Users wanting USB Gadgets will need to disable DM_USB and leave it the old way for now.
Change-Id: I07fd347129706d136fadd4d6aa735c5df95cb17e Signed-off-by: Adam Ford <aford173@gmail.com> Signed-off-by: Frank Wang <frank.wang@rock-chips.com> (cherry picked from commit 1a35526e1d54a346e12435bee757bfe47093157d)
show more ...
|
| ae6acf9f | 17-Nov-2016 |
Mugunthan V N <mugunthanvnm@ti.com> |
drivers: usb: musb: add ti musb host driver with driver model support
Add a TI MUSB host driver with driver model support and the driver will be bound by the MUSB wrapper driver based on the dr_mode
drivers: usb: musb: add ti musb host driver with driver model support
Add a TI MUSB host driver with driver model support and the driver will be bound by the MUSB wrapper driver based on the dr_mode device tree entry.
Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com>
show more ...
|
| 1cac34ce | 17-Nov-2016 |
Mugunthan V N <mugunthanvnm@ti.com> |
drivers: usb: musb: adopt musb backend driver to driver model
Currently all backend driver ops uses hard coded physical address, so to adopt the driver to DM, add device pointer to ops call backs so
drivers: usb: musb: adopt musb backend driver to driver model
Currently all backend driver ops uses hard coded physical address, so to adopt the driver to DM, add device pointer to ops call backs so that drivers can get physical addresses from the usb driver priv/plat data.
Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com>
show more ...
|