Hi,
Roger Quadros writes:
> Felipe,
>
> On 03/01/17 14:53, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Roger Quadros writes:
>>> Mathias & Felipe,
>>>
>>> On 17/11/16 17:01, Roger Quadros wrote:
Hi,
Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
If the
Felipe,
On 03/01/17 14:53, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> Mathias & Felipe,
>>
>> On 17/11/16 17:01, Roger Quadros wrote:
>>> Hi,
>>>
>>> Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
>>>
>>> If the attached high-speed device is misbehaving, the
On 03.01.2017 14:53, Felipe Balbi wrote:
Hi,
Roger Quadros writes:
Mathias & Felipe,
On 17/11/16 17:01, Roger Quadros wrote:
Hi,
Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
If the attached high-speed device is misbehaving, the USB stack typically
disables the por
Hi,
Roger Quadros writes:
> Mathias & Felipe,
>
> On 17/11/16 17:01, Roger Quadros wrote:
>> Hi,
>>
>> Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
>>
>> If the attached high-speed device is misbehaving, the USB stack typically
>> disables the port using the PED bit in
Mathias & Felipe,
On 17/11/16 17:01, Roger Quadros wrote:
> Hi,
>
> Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
>
> If the attached high-speed device is misbehaving, the USB stack typically
> disables the port using the PED bit in PORTSC. For the controllers that
> have
Hi,
Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
If the attached high-speed device is misbehaving, the USB stack typically
disables the port using the PED bit in PORTSC. For the controllers that
have broken port disable, the port fails to detect further attach/detach
even
6 matches
Mail list logo