hi Alan:
2014-04-09 6:58 GMT+08:00 Alan Stern :
> On Tue, 8 Apr 2014, vichy wrote:
>
>> > That's a different bit. USB_PORT_FEAT_C_RESET isn't the same as
>> > USB_PORT_FEAT_RESET.
>> what I am curious is,
>> if port reset bit will clear to 0 within 2ms, why we still need to
>> clear_port_feature
On Tue, 8 Apr 2014, vichy wrote:
> > That's a different bit. USB_PORT_FEAT_C_RESET isn't the same as
> > USB_PORT_FEAT_RESET.
> what I am curious is,
> if port reset bit will clear to 0 within 2ms, why we still need to
> clear_port_feature with USB_PORT_FEAT_C_RESET
> (clear Port reset )
> >
> >>
hi Alan:
2014-04-07 10:06 GMT+08:00 Alan Stern :
> On Sun, 6 Apr 2014, vichy wrote:
>
>> hi alan:
>> >> Why you think it is a bug in hardware?
>> >
>> > The timeout error means that the kernel told the controller to turn off
>> > the PORT_RESET bit, and 1000 us later the bit was still on. That's
On Sun, 6 Apr 2014, vichy wrote:
> hi alan:
> >> Why you think it is a bug in hardware?
> >
> > The timeout error means that the kernel told the controller to turn off
> > the PORT_RESET bit, and 1000 us later the bit was still on. That's a
> > hardware bug.
> after checking my hardware I found i
hi alan:
>> Why you think it is a bug in hardware?
>
> The timeout error means that the kernel told the controller to turn off
> the PORT_RESET bit, and 1000 us later the bit was still on. That's a
> hardware bug.
after checking my hardware I found if device is no connected and do
the port reset,
On Fri, 4 Apr 2014, vichy wrote:
> >> 1. Platform-ehci Platform-ehci.0: port 1 reset error -110
> >> the -110 is due to below handshake timeout.
> >> retval = handshake(ehci, status_reg,
> >> PORT_RESET, 0, 1000);
> >> if (retval != 0) {
> >>
hi Alan:
2014-04-04 8:48 GMT+08:00 Alan Stern :
> On Thu, 3 Apr 2014, vichy wrote:
>
>> I add more description.
>> in Below #1, since connect status is zero, handshake will fail with
>> return -ETIMEDOUT.
>> Then go to #2 error label.
>> and finally hub_port_status get -32, -EPIPE.
>>
>> 1. Platf
On Thu, 3 Apr 2014, vichy wrote:
> I add more description.
> in Below #1, since connect status is zero, handshake will fail with
> return -ETIMEDOUT.
> Then go to #2 error label.
> and finally hub_port_status get -32, -EPIPE.
>
> 1. Platform-ehci Platform-ehci.0: port 1 reset error -110
> th
hi Alan:
>> Your log contains the explanation:
>>
>>> Platform-ehci Platform-ehci.0: port 1 reset
>>
>> This is where the reset starts.
>>
>>> Platform-ehci Platform-ehci.0: in port reset sequence, GetStatus
>>> port:1 status 000100 0 ACK sig=se0 RESET
>>> usb 4-1: USB disconnect, device number 20
hi Alan:
2014-04-03 20:52 GMT+08:00 Alan Stern :
> On Thu, 3 Apr 2014, vichy wrote:
>
>> hi all:
>> I list my environment as below:
>> 1. Arm platform with ehci support
>> 2. plug in NTFS USB HD and play movie
>> 3. plug out device suddenly.
>>
>> I found there will be possibly that driver will re
On Thu, 3 Apr 2014, vichy wrote:
> hi all:
> I list my environment as below:
> 1. Arm platform with ehci support
> 2. plug in NTFS USB HD and play movie
> 3. plug out device suddenly.
>
> I found there will be possibly that driver will reset port even there
> is no device connected.
> I purposely
11 matches
Mail list logo
