linux-kernel - Re: [PATCH 1/9] dt-bindings: soc: qcom: eud: Restructure to model multi-path hardware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20260117-courageous-chamois-of-focus-20d5d5@quoll>
Date: Sat, 17 Jan 2026 12:57:58 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Elson Serrao <elson.serrao@....qualcomm.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
	Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Souradeep Chowdhury <quic_schowdhu@...cinc.com>, 
	linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-usb@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/9] dt-bindings: soc: qcom: eud: Restructure to model
 multi-path hardware

On Fri, Jan 16, 2026 at 03:20:58PM -0800, Elson Serrao wrote:
> The Qualcomm Embedded USB Debugger (EUD) hardware can intercept up to
> two independent High-Speed UTMI data paths, depending on the SoC
> configuration. Each path operates independently with:
> 
> - Dedicated PHY interface
> - Distinct USB connector and controller associations
> - Role dependent routing
> 
> Model these hardware paths as separate eud-path nodes to accurately
> represent the physical topology and add below per-path properties:
> 
> phys: EUD exposes a High-Speed debug hub that relies on HS-PHY for its
> operation. This property references the HS-PHY associated with the UTMI
> path.
> 
> usb-role-switch: Indicates that the USB port on this UTMI path supports
> role switching. In device role, debug mode inserts the EUD hub into the
> UTMI path. In host role, the EUD hub is bypassed and UTMI traffic flows
> directly between the PHY and the USB controller.
> 
> This change breaks backwards compatibility, but the previous binding
> omitted critical resources like PHY and did not describe per-path
> topology. Without these modifications EUD cannot be guaranteed to
> function.

It was working for 3 years, so your guarantees are just imprecise. FUD
is not an argument.

Qualcomm task at 2022 was to post complete bindings. These were posted
and accepted. Three years later you say that previous posting was
bollocks and this cannot even work?

Nah, take responsibility of what you did in the past.

Best regards,
Krzysztof