From: Bjorn Andersson <andersson@kernel.org>
To: Elson Serrao <elson.serrao@oss.qualcomm.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v7 1/8] dt-bindings: soc: qcom: eud: Add per-path child nodes for UTMI routing
Date: Mon, 31 Aug 2026 17:39:06 -0500 [thread overview]
Message-ID: <apYCal5G0S9cOWJf@baldur> (raw)
In-Reply-To: <20260831030147.1500616-2-elson.serrao@oss.qualcomm.com>
On Sun, Aug 30, 2026 at 08:01:40PM -0700, Elson Serrao wrote:
> The Qualcomm Embedded USB Debugger (EUD) can intercept one or two
> High-Speed UTMI paths depending on the SoC. For example, SC7280 supports
> EUD on the primary UTMI path only, while SM8350 supports EUD on both
> primary and secondary UTMI paths.
>
> Each UTMI path connects an independent USB controller/connector pair and
> forms its own role-switch domain. EUD routes traffic based on USB role.
> In device role the debug hub is inserted, while in host role it is
> bypassed.
>
> The existing binding models EUD using a flattened ports representation.
> While sufficient for fixed device-role configurations, it cannot naturally
> associate a controller, connector, and role switch with a specific
> EUD-routable path. This is problematic for role-switch capable ports and
> becomes more pronounced on SoCs with multiple paths. In such cases, each
> path forms an independent role-switch domain and requires per-path role
> awareness.
>
> Model each UTMI path as a separate child node with its own OF graph. This
> representation is used for role-aware EUD routing regardless of whether a
> SoC exposes one or two UTMI paths. Add an SM8350 compatible for
> dual-path EUD topologies. Retain support for the legacy flat ports
> representation on SC7280 for backward compatibility.
>
Acked-by: Bjorn Andersson <andersson@kernel.org>
Please merge this together with the driver changes.
Regards,
Bjorn
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
> ---
> .../bindings/soc/qcom/qcom,eud.yaml | 134 +++++++++++++++++-
> 1 file changed, 133 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> index 84218636c0d8..c377a77d623c 100644
> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> @@ -18,6 +18,7 @@ properties:
> items:
> - enum:
> - qcom,sc7280-eud
> + - qcom,sm8350-eud
> - const: qcom,eud
>
> reg:
> @@ -45,10 +46,88 @@ properties:
> $ref: /schemas/graph.yaml#/properties/port
> description: This port is to be attached to the type C connector.
>
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> +patternProperties:
> + "^eud-path@[0-1]$":
> + type: object
> + description:
> + Represents one High-Speed UTMI path that EUD intercepts. Use eud-path nodes
> + to associate role-switching behavior with specific port connections, allowing
> + EUD to manage role transitions independently for each UTMI path.
> +
> + properties:
> + reg:
> + maxItems: 1
> + description: Path number
> +
> + usb-role-switch:
> + type: boolean
> + description:
> + Indicates that EUD relays USB role-switch events for this path and
> + performs role-dependent UTMI routing accordingly. In device role,
> + the EUD hub is inserted into this path to enable debug
> + functionality. In host role, the EUD hub is bypassed and UTMI
> + traffic flows directly between the PHY and the USB controller.
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> + description:
> + These ports are to be attached to the endpoint of the USB controller node
> + and USB connector node.
> +
> + properties:
> + port@0:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: This port is to be attached to the USB controller.
> +
> + port@1:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: This port is to be attached to the USB connector.
> +
> + required:
> + - reg
> + - ports
> +
> + additionalProperties: false
> +
> required:
> - compatible
> - reg
> - - ports
> +
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,sc7280-eud
> + then:
> + oneOf:
> + - required:
> + - ports
> + properties:
> + eud-path@0: false
> + eud-path@1: false
> + - required:
> + - eud-path@0
> + properties:
> + ports: false
> + eud-path@1: false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,sm8350-eud
> + then:
> + required:
> + - eud-path@0
> + - eud-path@1
> + properties:
> + ports: false
>
> additionalProperties: false
>
> @@ -77,3 +156,56 @@ examples:
> };
> };
> };
> + - |
> + eud@88e0000 {
> + compatible = "qcom,sm8350-eud", "qcom,eud";
> + reg = <0x88e0000 0x2000>,
> + <0x88e2000 0x1000>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + eud-path@0 {
> + reg = <0>;
> + usb-role-switch;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + port@0 {
> + reg = <0>;
> + eud_usb0: endpoint {
> + remote-endpoint = <&usb_1_dwc3_hs>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> + eud_con0: endpoint {
> + remote-endpoint = <&pmic_glink_hs_in>;
> + };
> + };
> + };
> + };
> +
> + eud-path@1 {
> + reg = <1>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + port@0 {
> + reg = <0>;
> + eud_usb1: endpoint {
> + remote-endpoint = <&usb_2_dwc3_hs>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> + eud_con1: endpoint {
> + remote-endpoint = <&conn_2_hs_in>;
> + };
> + };
> + };
> + };
> + };
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-08-31 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 3:01 [PATCH v7 0/8] Improve Qualcomm EUD driver and platform support Elson Serrao
2026-08-31 3:01 ` [PATCH v7 1/8] dt-bindings: soc: qcom: eud: Add per-path child nodes for UTMI routing Elson Serrao
2026-08-31 22:39 ` Bjorn Andersson [this message]
2026-08-31 3:01 ` [PATCH v7 2/8] usb: misc: qcom_eud: add sysfs attribute for port selection Elson Serrao
2026-08-31 3:01 ` [PATCH v7 3/8] usb: misc: qcom_eud: add per-path High-Speed PHY control Elson Serrao
2026-08-31 3:01 ` [PATCH v7 4/8] usb: misc: qcom_eud: add per-path role switch support Elson Serrao
2026-08-31 3:01 ` [PATCH v7 5/8] usb: misc: qcom_eud: improve enable_store API Elson Serrao
2026-08-31 3:01 ` [PATCH v7 6/8] usb: misc: qcom_eud: add role-based EUD control Elson Serrao
2026-09-01 11:36 ` Konrad Dybcio
2026-08-31 3:01 ` [PATCH v7 7/8] usb: misc: qcom_eud: fix virtual attach/detach event handling Elson Serrao
2026-08-31 3:01 ` [PATCH v7 8/8] arm64: dts: qcom: kodiak: Desribe EUD UTMI routing and connector mapping Elson Serrao
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=apYCal5G0S9cOWJf@baldur \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=elson.serrao@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@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