From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: usb gadget on zaurus and kexec
Date: Thu, 10 Jun 2010 15:14:52 +0200 [thread overview]
Message-ID: <87wru7xc4z.fsf@free.fr> (raw)
In-Reply-To: <201006100900.23981.marek.vasut@gmail.com> (Marek Vasut's message of "Thu, 10 Jun 2010 09:00:23 +0200")
Marek Vasut <marek.vasut@gmail.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
WARNING: multiple messages have this Message-ID (diff)
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Eric Miao <eric.y.miao@gmail.com>,
dbaryshkov@gmail.com, Cyril Hrubis <metan@ucw.cz>,
arminlitzel@web.de, kernel list <linux-kernel@vger.kernel.org>,
utx@penguin.cz, lenz@cs.wisc.edu, rpurdie@rpsys.net, pave@ucw.cz,
thommycheck@gmail.com, zaurus-devel@www.linuxtogo.org,
omegamoon@gmail.com
Subject: Re: usb gadget on zaurus and kexec
Date: Thu, 10 Jun 2010 15:14:52 +0200 [thread overview]
Message-ID: <87wru7xc4z.fsf@free.fr> (raw)
In-Reply-To: <201006100900.23981.marek.vasut@gmail.com> (Marek Vasut's message of "Thu, 10 Jun 2010 09:00:23 +0200")
Marek Vasut <marek.vasut@gmail.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
next prev parent reply other threads:[~2010-06-10 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 15:46 usb gadget on zaurus and kexec Cyril Hrubis
2010-05-19 15:46 ` Cyril Hrubis
2010-05-20 5:05 ` Eric Miao
2010-05-20 5:05 ` Eric Miao
2010-06-10 6:10 ` Eric Miao
2010-06-10 6:10 ` Eric Miao
2010-06-10 7:00 ` Marek Vasut
2010-06-10 7:00 ` Marek Vasut
2010-06-10 13:14 ` Robert Jarzmik [this message]
2010-06-10 13:14 ` Robert Jarzmik
2010-07-13 11:26 ` Cyril Hrubis
2010-07-13 11:26 ` Cyril Hrubis
2010-07-13 16:47 ` Stanislav Brabec
2010-07-13 16:47 ` Stanislav Brabec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wru7xc4z.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.