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: <203eaca6-7631-42ae-af37-8affa76c44b9@gmail.com>
Date: Tue, 27 Feb 2024 15:51:08 +0100
From: Gabor Juhos <j4g8y7@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
 Conor Dooley <conor+dt@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
 Conor Dooley <conor.dooley@...rochip.com>,
 Konrad Dybcio <konrad.dybcio@...aro.org>,
 Bjorn Andersson <andersson@...nel.org>
Subject: Re: [PATCH v2 0/2] arm64: add minimal boot support for TP-Link Archer
 AX55 v1

Hello Rob,

2024. 02. 27. 14:45 keltezéssel, Rob Herring írta:

> My bot found new DT warnings on the .dts files added or changed in this
> series.
> 
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. 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
> 
> 
> New warnings running 'make CHECK_DTBS=y qcom/ipq5018-tplink-archer-ax55-v1.dtb' for 20240226-archer-ax55-v1-v2-0-3776eb61f432@...il.com:
> 
> arch/arm64/boot/dts/qcom/ipq5018-tplink-archer-ax55-v1.dtb: usb@...8800: interrupts: [[0, 62, 4]] is too short
> 	from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml#
> arch/arm64/boot/dts/qcom/ipq5018-tplink-archer-ax55-v1.dtb: usb@...8800: interrupt-names: ['hs_phy_irq'] is too short
> 	from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml#
> arch/arm64/boot/dts/qcom/ipq5018-tplink-archer-ax55-v1.dtb: usb@...8800: interrupts: [[0, 62, 4]] is too short
> 	from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml#
> arch/arm64/boot/dts/qcom/ipq5018-tplink-archer-ax55-v1.dtb: usb@...8800: interrupt-names:0: 'pwr_event' was expected
> 	from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml#
> arch/arm64/boot/dts/qcom/ipq5018-tplink-archer-ax55-v1.dtb: usb@...8800: interrupt-names: ['hs_phy_irq'] is too short
> 	from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml#
> 

These are caused by the 'usb@...8800' defined in the SoC .dtsi
(arch/arm64/boot/dts/qcom/ipq5018.dtsi) file. I saw the warnings, and I have
indicated that in the previous version of the patch [1].

Sorry, I should have kept that note in the current version as well.

Regards,
Gabor

1. https://lore.kernel.org/r/20240223-archer-ax55-v1-v1-2-99f8fa2c3858@gmail.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ