> On 2/28/19 1:57 AM, Peter Chen wrote:
> >
> >>> Let me summary your observation:
> >>> - bind/unbind ci_hdrc device can recover connection
> >>> - Reset HUB can't recover, and will go the previous error state
> >>> after reset
> >>>
> >>> From the register, we do see something abnormal, and t
On 2/28/19 1:57 AM, Peter Chen wrote:
Let me summary your observation:
- bind/unbind ci_hdrc device can recover connection
- Reset HUB can't recover, and will go the previous error state after
reset
From the register, we do see something abnormal, and the RX is
waiting the SYNC Field. We ne
> > Let me summary your observation:
> > - bind/unbind ci_hdrc device can recover connection
> > - Reset HUB can't recover, and will go the previous error state after
> > reset
> >
> > From the register, we do see something abnormal, and the RX is
> > waiting the SYNC Field. We need to see the d
On 2/27/19 2:22 AM, Peter Chen wrote:
Chandler
From the above, we know the controller is at RX active status. But I
am sorry I got the imprecise instruction from IC guys. The reason we
do that is to know the RX status change during one packet, for your
example, there are ISOC packets, so, m
> >> Chandler
> > From the above, we know the controller is at RX active status. But I
> > am sorry I got the imprecise instruction from IC guys. The reason we
> > do that is to know the RX status change during one packet, for your
> > example, there are ISOC packets, so, measure time is about 2
On 2/25/19 11:02 PM, Peter Chen wrote:
I suspect the controller is stuck at high speed. Chandler, would you please
supply
below information:
- If there is SOFs on the bus (you need to measure by probe) when the issue
occurs?
- If the SOF can't be observed at bus, it means the disconnection
can't
> > I suspect the controller is stuck at high speed. Chandler, would you please
> > supply
> below information:
> > - If there is SOFs on the bus (you need to measure by probe) when the issue
> occurs?
> > - If the SOF can't be observed at bus, it means the disconnection
> > can't be observed eith
On 2/24/19 9:58 PM, Peter Chen wrote:
I suspect the controller is stuck at high speed. Chandler, would you please
supply below information:
- If there is SOFs on the bus (you need to measure by probe) when the issue
occurs?
- If the SOF can't be observed at bus, it means the disconnection can't
> On 2/23/19 3:17 AM, Greg KH wrote:
> > On Fri, Feb 22, 2019 at 10:43:17AM -0500, Chandler Griscom wrote:
> >> Hello,
> >>
> >> I am encountering an issue where noise on USB devices is causing the
> >> host ci_hdrc driver to stall. The system contains an i.MX6 board
> >> (UDOO) connected to a U
On Sat, 23 Feb 2019, Chandler Griscom wrote:
> Yesterday I found this repeated message by enabling dynamic debugging
> for the chipidea and ehci modules; it might reveal something about
> where it gets stuck:
>
> ci_hdrc ci_hdrc.0: IAA watchdog: status ce088 cmd 10075 That seems to
> line up w
On 2/23/19 3:17 AM, Greg KH wrote:
On Fri, Feb 22, 2019 at 10:43:17AM -0500, Chandler Griscom wrote:
Hello,
I am encountering an issue where noise on USB devices is causing the
host ci_hdrc driver to stall. The system contains an i.MX6 board
(UDOO) connected to a USB touchscreen, SMSC95xx hub,
On Fri, Feb 22, 2019 at 10:43:17AM -0500, Chandler Griscom wrote:
> Hello,
>
> I am encountering an issue where noise on USB devices is causing the
> host ci_hdrc driver to stall. The system contains an i.MX6 board
> (UDOO) connected to a USB touchscreen, SMSC95xx hub, an FTDI device,
> and a hi-
12 matches
Mail list logo
