From: Ladislav Michl <oss-lists@triops.cz>
To: linux-usb@vger.kernel.org
Subject: Re: xHCI host dies on device unplug
Date: Tue, 6 Dec 2022 14:17:08 +0100 [thread overview]
Message-ID: <Y49A1Pv6dUScQ9x/@lenoch> (raw)
In-Reply-To: <Y45iXb6VCNiz7ZVd@lenoch>
On Mon, Dec 05, 2022 at 10:27:57PM +0100, Ladislav Michl wrote:
> I'm running current linux.git on custom Marvell OCTEON III CN7020
> based board. USB devices like FTDI (idVendor=0403, idProduct=6001,
> bcdDevice= 6.00) Realtek WiFi dongle (idVendor=0bda, idProduct=8179,
> bcdDevice= 0.00) works without issues, while Ralink WiFi dongle
> (idVendor=148f, idProduct=5370, bcdDevice= 1.01) kills the host on
> disconnect:
> xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command
> xhci-hcd xhci-hcd.0.auto: xHCI host controller not responding, assume dead
> xhci-hcd xhci-hcd.0.auto: HC died; cleaning up
>
> Unfortunately I do not have a datasheet for CN7020 SoC, so it is hard
> to tell if there is any errata :/ In case anyone see a clue in debug
> logs bellow, I'll happily give it a try.
So I do have datasheet now. As a wild guess I tried to use dlmc_ref_clk0
instead of dlmc_ref_clk1 as a refclk-type-ss and it fixed unplug death.
I have no clue why, but anyway - sorry for the noise :) Perhaps Octeon's
clock init is worth to be verified...
ladis
next prev parent reply other threads:[~2022-12-06 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 21:27 xHCI host dies on device unplug Ladislav Michl
2022-12-06 13:17 ` Ladislav Michl [this message]
2022-12-15 16:12 ` Ladislav Michl
2022-12-16 10:13 ` Mathias Nyman
2022-12-16 21:32 ` Ladislav Michl
2022-12-19 12:25 ` Mathias Nyman
2022-12-19 18:31 ` Ladislav Michl
2022-12-19 21:45 ` Ladislav Michl
2022-12-20 7:58 ` Ladislav Michl
2022-12-21 9:46 ` Mathias Nyman
2022-12-21 7:14 ` Ladislav Michl
2022-12-21 9:58 ` Mathias Nyman
2022-12-21 10:11 ` Ladislav Michl
2022-12-21 12:05 ` Ladislav Michl
2022-12-21 12:12 ` Mathias Nyman
2022-12-21 12:21 ` Ladislav Michl
2022-12-19 7:11 ` Ladislav Michl
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=Y49A1Pv6dUScQ9x/@lenoch \
--to=oss-lists@triops.cz \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).