From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] xHCI on x86
Date: Mon, 18 Jul 2016 12:42:47 +0200 [thread overview]
Message-ID: <578CB2A7.6010907@denx.de> (raw)
In-Reply-To: <CAPnjgZ1Fqk8jyxLRd1P2xgw0NSyCn+KtHj5cdupKEXxs=s3eMQ@mail.gmail.com>
Hi Simon,
On 15.07.2016 05:19, Simon Glass wrote:
> On 13 July 2016 at 00:20, Stefan Roese <sr@denx.de> wrote:
>> Hi!
>>
>> I'm currently trying to get xHCI working on some BayTrail based
>> x86 boards. For this I've added DM support to xhci-pci and made a
>> small change to cache.h to enable compilation of the xhci driver on
>> x86 (please find those 2 patches attached - I'll send then to the
>> list once this is resolved). But I noticed that the xhci driver
>> hangs in xhci_queue_command() in this line:
>>
>> xhci_writel(&ctrl->dba->doorbell[0], DB_VALUE_HOST);
>>
>> when first writing to the doorbell register. Reading from this doorbell
>> register still works just fine.
>>
>> IIRC, Simon has mentioned that xHCI still has some "issues" on x86.
>> Simon, is this what you have seen as well? Does anyone have some ideas
>> how to solve this?
>
> I'm really not sure what is wrong, sorry. The discussion about
> enabling the pin settings correctly may be relevant since I believe
> two GPIOs need to be set up for both ports to work, and that patch was
> never cleaned up and applied, so far as I know...
I see.
I my case, it's not related to the GPIO issue - as the ports are not
enabled via GPIO on the Congatec board where I'm currently testing on.
I've updated the xHCI PCI support a bit (no hangup any more, but still
not working correctly) and will post the current version as WIP today,
as I need to switch to some other tasks for a while. Perhaps someone
else is interested in xHCI on x86 enough to take a look at it in the
meantime...
Thanks,
Stefan
prev parent reply other threads:[~2016-07-18 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 6:20 [U-Boot] xHCI on x86 Stefan Roese
2016-07-15 3:19 ` Simon Glass
2016-07-18 10:42 ` Stefan Roese [this message]
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=578CB2A7.6010907@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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