Searched hist:ba55453ccf6d82c46b9f3eef5b958aac58adb6fb (Results 1 – 4 of 4) sorted by relevance
| /rk3399_rockchip-uboot/include/linux/usb/ |
| H A D | xhci-omap.h | ba55453ccf6d82c46b9f3eef5b958aac58adb6fb Fri Oct 11 17:28:16 UTC 2013 Dan Murphy <dmurphy@ti.com> usb: omap: Move the usb phy code to the usb/phy directory
Moving the usb/phy code from xhci-omap to the usb/phy directory
and moving the associated phy code over to the new file.
Newer TI processors adding xHCI support will have different PHY configurations
so therefore abstracting this code away will prevent messing around with the
xhci-omap file itself.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
| /rk3399_rockchip-uboot/drivers/usb/phy/ |
| H A D | Makefile | ba55453ccf6d82c46b9f3eef5b958aac58adb6fb Fri Oct 11 17:28:16 UTC 2013 Dan Murphy <dmurphy@ti.com> usb: omap: Move the usb phy code to the usb/phy directory
Moving the usb/phy code from xhci-omap to the usb/phy directory
and moving the associated phy code over to the new file.
Newer TI processors adding xHCI support will have different PHY configurations
so therefore abstracting this code away will prevent messing around with the
xhci-omap file itself.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
| H A D | omap_usb_phy.c | ba55453ccf6d82c46b9f3eef5b958aac58adb6fb Fri Oct 11 17:28:16 UTC 2013 Dan Murphy <dmurphy@ti.com> usb: omap: Move the usb phy code to the usb/phy directory
Moving the usb/phy code from xhci-omap to the usb/phy directory
and moving the associated phy code over to the new file.
Newer TI processors adding xHCI support will have different PHY configurations
so therefore abstracting this code away will prevent messing around with the
xhci-omap file itself.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
| /rk3399_rockchip-uboot/drivers/usb/host/ |
| H A D | xhci-omap.c | ba55453ccf6d82c46b9f3eef5b958aac58adb6fb Fri Oct 11 17:28:16 UTC 2013 Dan Murphy <dmurphy@ti.com> usb: omap: Move the usb phy code to the usb/phy directory
Moving the usb/phy code from xhci-omap to the usb/phy directory
and moving the associated phy code over to the new file.
Newer TI processors adding xHCI support will have different PHY configurations
so therefore abstracting this code away will prevent messing around with the
xhci-omap file itself.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|