linux-kernel - Re: [PATCH v2 0/2] Flatten usb controller nodes on Talos

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <176961029843.1671023.5334223517300256096.robh@kernel.org>
Date: Wed, 28 Jan 2026 08:27:06 -0600
From: Rob Herring <robh@...nel.org>
To: Krishna Kurapati <krishna.kurapati@....qualcomm.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>, 
 Bjorn Andersson <andersson@...nel.org>, 
 Konrad Dybcio <konradybcio@...nel.org>, linux-kernel@...r.kernel.org, 
 Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2 0/2] Flatten usb controller nodes on Talos

On Wed, 28 Jan 2026 11:57:18 +0530, Krishna Kurapati wrote:
> Flatten usb controller node and update to using latest bindings and
> flattened driver approach. While at it, add the wakeup-source property
> to usb controller nodes.
> 
> Changes in v2:
> Reversed order of patches as per comment from Dmitry
> 
> Link to v1:
> https://lore.kernel.org/all/20260127155537.4088709-1-krishna.kurapati@oss.qualcomm.com/
> 
> Krishna Kurapati (2):
>   arm64: dts: qcom: talos: Flatten usb controller nodes
>   arm64: dts: qcom: talos: Mark usb controllers are wakeup capable
>     devices
> 
>  arch/arm64/boot/dts/qcom/qcs615-ride.dts | 12 +--
>  arch/arm64/boot/dts/qcom/talos.dtsi      | 97 ++++++++++--------------
>  2 files changed, 46 insertions(+), 63 deletions(-)
> 
> --
> 2.34.1
> 
> 
> 

My bot found DTB warnings on the .dts/.dtsi files added or changed in
this series.

Some warnings may be existing warnings. Consider fixing existing
warnings before adding new features.

Perhaps the warnings are fixed by another series. If that is the case,
please set the base commit and any dependencies for the series using
"b4".

Ultimately, it is up to the platform maintainer whether these warnings
are acceptable or not.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade

This patch series was applied (using b4) to base:
 Base: attempting to guess base-commit...
 Base: tags/next-20260127 (exact match)
 Base: tags/next-20260127 (use --merge-base to override)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20260128062720.437712-1-krishna.kurapati@....qualcomm.com:

arch/arm64/boot/dts/qcom/qcs615-ride.dtb: clock-controller@...000 (qcom,qcs615-gcc): 'clock-names' is a required property
	from schema $id: http://devicetree.org/schemas/clock/qcom,qcs615-gcc.yaml