Hello,
I have some pxa270 based single board computers which have an
IT8152G companion chip. This chip has a built-in USB Host controller
which is (according to the datasheet) register compatible with OHCI
specification version 1.0.
During boot, I see that the OHCI controller is detected proper
On Tue, 13 Feb 2007, Raphael Assenat wrote:
> Hello,
> I have some pxa270 based single board computers which have an
> IT8152G companion chip. This chip has a built-in USB Host controller
> which is (according to the datasheet) register compatible with OHCI
> specification version 1.0.
>
> Dur
Alan Stern wrote:
> On Tue, 13 Feb 2007, Raphael Assenat wrote:
>>I have some pxa270 based single board computers which have an
>>IT8152G companion chip. This chip has a built-in USB Host controller
>>which is (according to the datasheet) register compatible with OHCI
>>specification version 1.0
On Wed, 14 Feb 2007, Raphael Assenat wrote:
> > Is that true even if there was also a device attached at boot time, or
> > does it happen only when you connect a new device and all the ports are
> > unoccupied?
> I had not thought of trying that... I did some tests and found that
> if a device
Alan Stern wrote:
> On Wed, 14 Feb 2007, Raphael Assenat wrote:
>
>
>>>Is that true even if there was also a device attached at boot time, or
>>>does it happen only when you connect a new device and all the ports are
>>>unoccupied?
>>
>>I had not thought of trying that... I did some tests and f
On Thu, 15 Feb 2007, Raphael Assenat wrote:
> > Okay. This says that RHSC works correctly while the controller is
> > running, but it doesn't work when the controller is suspended.
> hmm. So that's a bug in the chip? Would preventing this specific
> controller from being suspended be an accepta
Alan Stern wrote:
On Thu, 15 Feb 2007, Raphael Assenat wrote:
Okay. This says that RHSC works correctly while the controller is
running, but it doesn't work when the controller is suspended.
hmm. So that's a bug in the chip? Would preventing this specific
controller from being suspended be
On Mon, 19 Feb 2007, Raphael Assenat wrote:
> > Wow, that's really buggy! Not only is there no interrupt request, the
> > port status shows that the chip doesn't even know you plugged in the
> > device.
> >
> > Clearly the chip's wakeup function is completely broken. The only way you
> > can ge
On Monday 19 February 2007 8:59 am, Raphael Assenat wrote:
> How about adding an OHCI_QUIRK_NO_RH_SUSPEND flag in struct ohci_hcd
> and using it to disable suspend for this chip? The flag can be set
> automatically in ohci-pci.c. The only thing I'm not sure about is
> the appropriate place to
David Brownell wrote:
On Monday 19 February 2007 8:59 am, Raphael Assenat wrote:
How about adding an OHCI_QUIRK_NO_RH_SUSPEND flag in struct ohci_hcd
and using it to disable suspend for this chip? The flag can be set
automatically in ohci-pci.c. The only thing I'm not sure about is
the appr
10 matches
Mail list logo
