linux-kernel - Re: [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties

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: <175625023024.716358.4095639193170110202.robh@kernel.org>
Date: Tue, 26 Aug 2025 18:19:44 -0500
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Alexander Stein <alexander.stein@...tq-group.com>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>, devicetree@...r.kernel.org, 
 Tony Lindgren <tony@...mide.com>, linux-kernel@...r.kernel.org, 
 linux-omap@...r.kernel.org, Conor Dooley <conor+dt@...nel.org>
Subject: Re: [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt
 properties


On Tue, 26 Aug 2025 15:42:57 +0200, Alexander Stein wrote:
> The binding document ti,tps65910.yaml requires the controller and
> cells properties for both gpio and interrupts. As they have const and
> fixed values a default can be provided for all users.
> 
> Signed-off-by: Alexander Stein <alexander.stein@...tq-group.com>
> ---
>  arch/arm/boot/dts/tps65910.dtsi | 4 ++++
>  1 file changed, 4 insertions(+)
> 


My bot found new DTB 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. No need to reply
unless the platform maintainer has comments.

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-20250825 (exact match)

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/arm/boot/dts/ti/' for 20250826134259.2564191-1-alexander.stein@...tq-group.com:

arch/arm/boot/dts/ti/omap/am335x-pdu001.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-base0033.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-baltos-ir5221.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-regor-rdk.dtb: pmic@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-netcom-plus-8xx.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-evm.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-evmsk.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/omap3-echo.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-moxa-uc-8100-me-t.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-icev2.dtb: power-controller@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-phycore-rdk.dtb: pmic@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am3517-craneboard.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-netcom-plus-2xx.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-netcan-plus-1xx.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-baltos-ir3220.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-wega-rdk.dtb: pmic@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-baltos-ir2110.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#
arch/arm/boot/dts/ti/omap/am335x-lxm.dtb: tps@2d (ti,tps65910): #interrupt-cells: 2 was expected
	from schema $id: http://devicetree.org/schemas/mfd/ti,tps65910.yaml#