[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wru7xc4z.fsf@free.fr>
Date: Thu, 10 Jun 2010 15:14:52 +0200
From: Robert Jarzmik <robert.jarzmik@...e.fr>
To: Marek Vasut <marek.vasut@...il.com>
Cc: linux-arm-kernel@...ts.infradead.org,
Eric Miao <eric.y.miao@...il.com>, dbaryshkov@...il.com,
Cyril Hrubis <metan@....cz>, arminlitzel@....de,
kernel list <linux-kernel@...r.kernel.org>, utx@...guin.cz,
lenz@...wisc.edu, rpurdie@...ys.net, pave@....cz,
thommycheck@...il.com, zaurus-devel@...ts.linuxtogo.org,
omegamoon@...il.com
Subject: Re: usb gadget on zaurus and kexec
Marek Vasut <marek.vasut@...il.com> writes:
>> > Dumping out the registers of the two situations and doing a comparison
>> > then might be a quick way.
>>
>> Any debugging update on this?
>
> Yeah, there's a workaround. Cyril's working on a proper fix, but that might take
> some time. Simply -- UP2OCR is misconfigured.
That's quite interesting. In the pxa27x_udc gadget driver, I seem to have a
regression on the resume from suspend to RAM path. My USB UDC is not enumerated
anymore.
The might be a correlation, as UP2OCR is lost in the suspend process. I'm very
interested by your analysis of the issue you have on kexec, as that might ease
my work :)
Besides, it's been some time I've been thinking that the pxa deserves a proper
encapsulation of the USB internal routing paths (ie. a proper way to switch from
usb host handled by ohci-pxa27x to an usb client handled by pxa2x_udc), to
reflect the setup of the Pad Unit (see TRM chapter 12.4 : tables 12.2, 12.15,
12.17, 12.18 and 12.19).
Whatever you find on the USB Port2 configuration register would help me design
the Pad block.
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists