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: <20251204-fierce-cuttlefish-of-election-c00c01@quoll>
Date: Thu, 4 Dec 2025 08:59:03 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>
To: "Rob Herring (Arm)" <robh@...nel.org>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, 
	Odelu Kukatla <odelu.kukatla@....qualcomm.com>, linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, 
	Georgi Djakov <djakov@...nel.org>, Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH] dt-bindings: interconnect: qcom,sa8775p-rpmh: Fix
 incorrectly added reg and clocks

On Sat, Nov 29, 2025 at 05:22:15AM -0600, Rob Herring (Arm) wrote:
> 
> On Sat, 29 Nov 2025 10:46:13 +0100, Krzysztof Kozlowski wrote:
> > Commit 8a55fbe4c94d ("dt-bindings: interconnect: add reg and clocks
> > properties to enable QoS on sa8775p") claims that all interconnects have
> > clocks and MMIO address space, but that is just not true.  Only few
> > have.  Bindings should restrict properties and should not allow
> > specifying non-existing hardware description, so fix missing constraints
> > for 'reg' and 'clocks'.
> > 
> > Fixes: 8a55fbe4c94d ("dt-bindings: interconnect: add reg and clocks properties to enable QoS on sa8775p")
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>
> > ---
> >  .../interconnect/qcom,sa8775p-rpmh.yaml       | 31 +++++++++++++++++++
> >  1 file changed, 31 insertions(+)
> > 
> 
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> 

These are bot hiccups due to broken way of applying of Qualcomm tsens
patch. False positives.

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ