From: Vadim Lobanov <vlobanov@speakeasy.net>
To: Thomas Dahlmann <dahlmann.thomas@arcor.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: amd5536udc interrupts bug
Date: Mon, 12 Jan 2009 11:02:45 -0800 [thread overview]
Message-ID: <200901121102.45783.vlobanov@speakeasy.net> (raw)
In-Reply-To: <496904E4.2000701@arcor.de>
On Saturday 10 January 2009 12:28:20 Thomas Dahlmann wrote:
> Vadim Lobanov schrieb:
> > Nope, nothing at all shows up in the logs or the interrupt counts when
> > the cable is plugged, neither for the host drivers nor the device
> > drivers. (The quickest test I have is to hook the device up to itself -
> > one A port and one B port.)
> >
> > The BIOS is configured "correctly" if the manuals are to be trusted. Here
> > are the relevant settings
> > OHCI: Enabled
> > EHCI: Enabled
> > UDC: Enabled
> > UOC: Disabled
> > Overcurrent reporting: Disabled
> > Port 4 assignment: Device
>
> UOC has to be enabled. This controller switches the UDC PHY to port 4
> and owns the mentioned
> PAD_EN and APU bits. These bits live in the memory mapped register space
> of UOC. I use a
> company intern tools to look at memory spaces of PCI devices. Lets
> forget these bits so far as I am
> pretty sure that enabling UOC fixes the problem.
That'll teach me for trusting the board vendor's documentation. :)
[ ... doing some tests ... ]
Unfortunately, however, even enabling UOC in the BIOS does not make the
USB connection work. The symptoms are exactly the same as before.
I'm going to try to figure out how to get at those two bits, and also will
start talking with the board vendor as well (since it's starting to look more
and more like a BIOS and/or HW problem).
Thanks for your help so far!
next prev parent reply other threads:[~2009-01-12 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49661E83.2070703@arcor.de>
2009-01-08 16:40 ` Thomas Dahlmann
2009-01-08 18:27 ` Vadim Lobanov
2009-01-09 2:02 ` Vadim Lobanov
2009-01-09 11:41 ` Thomas Dahlmann
2009-01-09 22:40 ` Vadim Lobanov
2009-01-10 20:28 ` Thomas Dahlmann
2009-01-12 19:02 ` Vadim Lobanov [this message]
2009-01-13 19:19 ` Vadim Lobanov
2009-01-14 12:43 ` Thomas Dahlmann
2009-01-14 22:49 ` Vadim Lobanov
2009-01-15 9:26 ` Thomas Dahlmann
2009-01-17 0:17 ` Vadim Lobanov
2009-01-19 12:23 ` Thomas Dahlmann
2009-01-07 23:10 Vadim Lobanov
2009-01-08 2:32 ` Robert Hancock
2009-01-08 3:30 ` Vadim Lobanov
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=200901121102.45783.vlobanov@speakeasy.net \
--to=vlobanov@speakeasy.net \
--cc=dahlmann.thomas@arcor.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®