Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org,  Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org,  linux-omap@vger.kernel.org,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties
Date: Tue, 26 Aug 2025 18:19:44 -0500	[thread overview]
Message-ID: <175625023024.716358.4095639193170110202.robh@kernel.org> (raw)
In-Reply-To: <20250826134259.2564191-1-alexander.stein@ew.tq-group.com>


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@ew.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@ew.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#






  parent reply	other threads:[~2025-08-26 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26 13:42 [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties Alexander Stein
2025-08-26 13:42 ` [PATCH 2/2] ARM: dts: am33xx-l4: Drop ti,omap3-uart entry from UART nodes Alexander Stein
2025-08-26 23:19 ` Rob Herring (Arm) [this message]
2025-08-27  6:05 ` [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties Alexander Stein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=175625023024.716358.4095639193170110202.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox