On Tue, Nov 25, 2014 at 5:32 AM, Jassi Brar <jaswinder.singh@xxxxxxxxxx> wrote: > On 25 November 2014 at 05:47, Andrew Bresticker <abrestic@xxxxxxxxxxxx> wrote: >> This series adds support for xHCI on NVIDIA Tegra SoCs. This includes: >> - patches 1, 2, and 3: minor cleanups for mailbox framework and xHCI, >> - patches 4 and 5: adding a driver for the mailbox used to communicate >> with the xHCI controller's firmware, >> - patches 6 and 7: extending the XUSB pad controller driver to support >> the USB PHY types (UTMI, HSIC, and USB3), >> - patches 8 and 9: adding a xHCI host-controller driver, and >> - patches 10, 11, and 12: updating the relevant DT files. >> >> The mailbox driver (patch 5) has a compile-time dependency on patch 2 and >> a run-time dependency on patch 3. Both the PHY (patch 7) and host (patch 9) >> drivers have compile-time dependencies on the mailbox driver. The host >> driver also has a run-time dependency on patch 1. Because of this, this >> entire series should probably go through the Tegra tree. >> > Why shouldn't I pick 2 & 3 at least? I don't see why not. Because of the PHY API change I'm going to have to re-spin the series and at this point 3.19 is looking pretty unlikely. Maybe we could get a Tegra maintainer's ACK for patches 4 and 5 so that you could take them through your tree as well for 3.19? (Stephen, Thierry, Alex?) -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
