From: Rob Herring <robh@kernel.org>
To: Alexander Wilhelm <alexander.wilhelm@westermo.com>,
Laurentiu Tudor <laurentiu.tudor@nxp.com>,
Li Yang <leoyang.li@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: USB error on LS1046 platform
Date: Tue, 27 Jan 2026 20:10:00 -0600 [thread overview]
Message-ID: <20260128021000.GA3716747-robh@kernel.org> (raw)
In-Reply-To: <aXh1kjRoGrj0SAyU@FUE-ALEWI-WINX>
+Laurentiu, Li
On Tue, Jan 27, 2026 at 09:21:38AM +0100, Alexander Wilhelm wrote:
> Hello developers,
>
> I’m using an NXP LS1046A SoC with the integrated DWC3 USB controller in
> host mode. On Linux v5.5.167 my USB flash drive was detected and mountable.
> After upgrading to Linux v6.6.110 the USB flash drive is no longer
> recognized. If it is already plugged in during boot phase I get the
> following errors:
>
> xhci-hcd xhci-hcd.2.auto: Error while assigning device slot ID: Command Aborted
> xhci-hcd xhci-hcd.2.auto: Max number of devices this xHCI host supports is 127
>
> I have narrowed the issue down to the following commit:
>
> 136975c33894e7b48a6007af0f4c25f423bbd1de
> arm64: dts: ls1046a: make dma-coherent global to the SoC
It's best to send this to the author(s) of the commit.
Looks like it needs to be reverted or USB marked non-coherent. That's
Shawn's responsibility to apply and the author to send a fix (unless
you want to). The DT maintainers don't take .dts patches.
>
> When I revert this commit, USB works perfectly on my system.
>
> I have already asked on the `linux-usb` mailing list
> (https://lore.kernel.org/linux-usb/aTFr17xKxnWGG3vU@FUE-ALEWI-WINX/) and also
> forwarded the message to `linux-arm-kernel`, but I haven’t received any replies
> so far. Has anyone encountered this problem on the LS1046 or a similar platform?
> Any hints or experiences would be greatly appreciated.
>
>
> Best regards
> Alexander Wilhelm
prev parent reply other threads:[~2026-01-28 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:21 USB error on LS1046 platform Alexander Wilhelm
2026-01-28 2:10 ` Rob Herring [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=20260128021000.GA3716747-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexander.wilhelm@westermo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@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 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.