Re: [PATCH v8 0/9] Tegra xHCI support

[Jon Hunter]

Hi Thierry,

On 05/05/15 15:42, Thierry Reding wrote:
> * PGP Signed by an unknown key
> 
> On Tue, May 05, 2015 at 03:28:25PM +0100, Jon Hunter wrote:
>> Hi Andrew,
>>
>> On 04/05/15 18:36, Andrew Bresticker 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 an MFD driver for the XUSB cmoplex,
>>>  - patches 6 and 7: adding a driver for the mailbox used to communicate
>>>    with the xHCI controller's firmware, and
>>>  - patches 8 and 9: adding a xHCI host-controller driver.
>>>
>>> The addition of USB PHY support to the XUSB padctl driver has been dropped.
>>> Thierry will be posting those patches later.
>>>
>>> Given the many compile and run-time dependencies in this series, it is probably
>>> best if the first 3 patches are picked up by the relevant maintainers in topic
>>> branches so that the remainder of the series can go through the Tegra tree.
>>>
>>> Tested on Jetson TK1 and Nyan-Big with a variety of USB2.0 and USB3.0 memory
>>> sticks and ethernet dongles.  This has also been tested, with additional
>>> out-of-tree patches, on Tegra132 and Tegra210 based boards.
>>
>> For the series, you can add my ...
>>
>> Reviewed-by: Jon Hunter <jonathanh@xxxxxxxxxx>
>> Tested-by: Jon Hunter <jonathanh@xxxxxxxxxx>
>>
>> I have tested this on a t124 nyan-big with USB3.0 and USB2.0 devices.
> 
> How can this be tested without the corresponding USB PHY patches that
> I'm supposed to be sending out?
> 
> Also, can anyone point me at patches that add the device tree nodes
> which this driver makes use of?

Andrew has a branch here [1] for testing this series. Yes, obviously
testing without your PHY piece (which I should have mentioned), but at
least we can test Andrew's changes.

Cheers
Jon

[1] https://github.com/abrestic/linux/tree/tegra-xhci-v8-test
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/