From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Felipe Balbi" <balbi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Sven Peter" <sven@kernel.org>, "Janne Grunau" <j@jannau.net>,
"Neal Gompa" <neal@gompa.dev>, "Joel Stanley" <joel@jms.id.au>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Ryan Chen" <ryan_chen@aspeedtech.com>,
"Billy Tsai" <billy_tsai@aspeedtech.com>,
"Michal Simek" <michal.simek@amd.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Yixun Lan" <dlan@kernel.org>,
"Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
"Minda Chen" <minda.chen@starfivetech.com>,
"Shyam Pandey" <radhey.shyam.pandey@amd.com>,
"Wei Yang" <yangwei1@eswincomputing.com>,
"Senchuan Zhang" <zhangsenchuan@eswincomputing.com>,
"Hang Cao" <caohang@eswincomputing.com>,
"Li Jun" <jun.li@nxp.com>, "Peng Fan" <peng.fan@nxp.com>,
"Roy Luo" <royluo@google.com>,
"Yang Xiwen" <forbidden405@foxmail.com>,
"Ahmad Zainie" <wan.ahmad.zainie.wan.mohamad@intel.com>,
"Robert Marko" <robert.marko@sartura.hr>,
"Xu Yang" <xu.yang_2@nxp.com>,
"Wesley Cheng" <quic_wcheng@quicinc.com>,
"Stanley Chang" <stanley_chang@realtek.com>,
"Ze Huang" <huang.ze@linux.dev>,
"Aswath Govindraju" <a-govindraju@ti.com>,
"Roger Quadros" <rogerq@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
asahi@lists.linux.dev, linux-aspeed@lists.ozlabs.org,
imx@lists.linux.dev, linux-samsung-soc@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-rockchip@lists.infradead.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
"Mathias Nyman" <mathias.nyman@intel.com>
Subject: Re: [PATCH 2/2] dt-bindings: usb: snps,dwc3: Fix downstream port numbering
Date: Wed, 21 Oct 2026 11:44:31 +0200 [thread overview]
Message-ID: <8ceba969-91d2-4b43-81d0-b26e7139664b@oss.qualcomm.com> (raw)
In-Reply-To: <CAGXv+5G_ig=k-eH8Cp0ES70WxTHcBS2TVj9VmHaG9caROiAuQQ@mail.gmail.com>
On 10/15/26 11:00 AM, Chen-Yu Tsai wrote:
> (Cc-ed Mathias, the xHCI driver maintainer in case I misunderstood xHCI.)
>
> On Thu, Oct 15, 2026 at 4:44 PM Neil Armstrong
> <neil.armstrong@linaro.org> wrote:
>>
>> On 10/14/26 18:36, Konrad Dybcio wrote:
>>> On 10/14/26 11:44 AM, Neil Armstrong wrote:
>>>> On 10/14/26 11:29, Chen-Yu Tsai wrote:
>>>>> On Wed, Oct 14, 2026 at 5:28 PM Neil Armstrong
>>>>> <neil.armstrong@linaro.org> wrote:
[...]
>> How about the USB4, does it use the USB3.0 port ?
>
> I'm not familiar with USB4. A quick search says that it can tunnel
> USB 3.x, DP, and PCIe, and it doesn't have its own USB HCI defined.
>
> So I'm thinking the USB4 controller would be more like a nexus node
> or multiplexing node, or perhaps like a USB C connector. It has input
> ports for all the protocols it can tunnel, connected to their respective
> controllers (XHCI, DP, PCIe). The binding probably would be very messy
> if one controller supported multiple outgoing ports, as each downstream
> port has a 3-to-1 relationship with its respective upstream protocol
> interfaces.
Yeah that is more or less it.
There needs to be a connection between the USB4 router and the native
(USB3 *port*, not hub | PCIe *port*, not RC | DPTX) protocol adapter
where the tunneled packets end up at to create a PM devlink between it
and the USB4 router.
ACPI does that by adding a `usb4-host-interface = &reference_to_router`
property, for DT that's still undecided:
https://github.com/devicetree-org/dt-schema/pull/196
As far as the Qualcomm implementation goes, I was hoping we could
go forward with base1 numbering as the DWC3 is an XHCI controller:
https://lore.kernel.org/linux-usb/20260929-topic-dwc3_tunneling_state-v4-0-63e296346d57@oss.qualcomm.com/
Konrad
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-10-21 9:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 8:20 [PATCH 0/2] dt-bindings: usb: downstream host ports for hcd and dwc3 Chen-Yu Tsai
2026-10-14 8:20 ` [PATCH 1/2] dt-bindings: usb: hcd: Add downstream USB ports Chen-Yu Tsai
2026-10-14 8:31 ` sashiko-bot
2026-10-14 10:16 ` Chen-Yu Tsai
2026-10-14 8:20 ` [PATCH 2/2] dt-bindings: usb: snps,dwc3: Fix downstream port numbering Chen-Yu Tsai
2026-10-14 8:28 ` Neil Armstrong
2026-10-14 9:29 ` Chen-Yu Tsai
2026-10-14 9:44 ` Neil Armstrong
2026-10-14 10:14 ` Chen-Yu Tsai
2026-10-14 12:15 ` Neil Armstrong
2026-10-14 16:36 ` Konrad Dybcio
2026-10-15 7:44 ` Neil Armstrong
2026-10-15 9:00 ` Chen-Yu Tsai
2026-10-21 9:44 ` Konrad Dybcio [this message]
2026-10-14 8:31 ` sashiko-bot
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=8ceba969-91d2-4b43-81d0-b26e7139664b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Frank.Li@nxp.com \
--cc=a-govindraju@ti.com \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=andrew@codeconstruct.com.au \
--cc=asahi@lists.linux.dev \
--cc=balbi@kernel.org \
--cc=billy_tsai@aspeedtech.com \
--cc=caohang@eswincomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=festevam@gmail.com \
--cc=forbidden405@foxmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=heiko@sntech.de \
--cc=huang.ze@linux.dev \
--cc=imx@lists.linux.dev \
--cc=j@jannau.net \
--cc=jbrunet@baylibre.com \
--cc=joel@jms.id.au \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mathias.nyman@intel.com \
--cc=mhiramat@kernel.org \
--cc=michal.simek@amd.com \
--cc=minda.chen@starfivetech.com \
--cc=neal@gompa.dev \
--cc=neil.armstrong@linaro.org \
--cc=peng.fan@nxp.com \
--cc=peter.griffin@linaro.org \
--cc=quic_wcheng@quicinc.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=royluo@google.com \
--cc=ryan_chen@aspeedtech.com \
--cc=s.hauer@pengutronix.de \
--cc=spacemit@lists.linux.dev \
--cc=stanley_chang@realtek.com \
--cc=sven@kernel.org \
--cc=troy.mitchell@linux.spacemit.com \
--cc=tudor.ambarus@linaro.org \
--cc=wan.ahmad.zainie.wan.mohamad@intel.com \
--cc=wenst@chromium.org \
--cc=xu.yang_2@nxp.com \
--cc=yangwei1@eswincomputing.com \
--cc=zhangsenchuan@eswincomputing.com \
/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®