Searched hist:"1 cac34ce161ae010d3f9ffd3f664e70206638ebc" (Results 1 – 6 of 6) sorted by relevance
| /rk3399_rockchip-uboot/arch/arm/mach-omap2/omap3/ |
| H A D | am35x_musb.c | 1cac34ce161ae010d3f9ffd3f664e70206638ebc Thu Nov 17 09:08:10 UTC 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 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>
|
| /rk3399_rockchip-uboot/arch/arm/include/asm/arch-omap3/ |
| H A D | musb.h | 1cac34ce161ae010d3f9ffd3f664e70206638ebc Thu Nov 17 09:08:10 UTC 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 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>
|
| /rk3399_rockchip-uboot/arch/arm/include/asm/ |
| H A D | omap_musb.h | 1cac34ce161ae010d3f9ffd3f664e70206638ebc Thu Nov 17 09:08:10 UTC 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 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>
|
| /rk3399_rockchip-uboot/drivers/usb/musb-new/ |
| H A D | am35x.c | 1cac34ce161ae010d3f9ffd3f664e70206638ebc Thu Nov 17 09:08:10 UTC 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 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>
|
| H A D | musb_dsps.c | 1cac34ce161ae010d3f9ffd3f664e70206638ebc Thu Nov 17 09:08:10 UTC 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 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>
|
| /rk3399_rockchip-uboot/arch/arm/mach-omap2/am33xx/ |
| H A D | board.c | 1cac34ce161ae010d3f9ffd3f664e70206638ebc Thu Nov 17 09:08:10 UTC 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 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>
|