* [PATCH 2/2] ARM: dts: am33xx-l4: Drop ti,omap3-uart entry from UART nodes
2025-08-26 13:42 [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties Alexander Stein
@ 2025-08-26 13:42 ` Alexander Stein
2025-08-26 23:19 ` [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties Rob Herring (Arm)
2025-08-27 6:05 ` Alexander Stein
2 siblings, 0 replies; 4+ messages in thread
From: Alexander Stein @ 2025-08-26 13:42 UTC (permalink / raw)
To: Tony Lindgren, Rob Herring, Krzysztof Kozlowski, Conor Dooley
Cc: Alexander Stein, linux-omap, devicetree, linux-kernel
ti,omap3-uart was kept around to work with legacy omap-serial driver.
Now that we have completed move to 8250-omap.c drop legacy compatible.
This follows along commit 40a95e2915e3f ("ARM: dts: am437x-l4: Drop
ti,omap2-uart entry from UART nodes")
Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
---
arch/arm/boot/dts/ti/omap/am33xx-l4.dtsi | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/ti/omap/am33xx-l4.dtsi b/arch/arm/boot/dts/ti/omap/am33xx-l4.dtsi
index d6a143abae5f6..cef24aafed1a8 100644
--- a/arch/arm/boot/dts/ti/omap/am33xx-l4.dtsi
+++ b/arch/arm/boot/dts/ti/omap/am33xx-l4.dtsi
@@ -200,7 +200,7 @@ SYSC_OMAP2_SOFTRESET |
ranges = <0x0 0x9000 0x1000>;
uart0: serial@0 {
- compatible = "ti,am3352-uart", "ti,omap3-uart";
+ compatible = "ti,am3352-uart";
clock-frequency = <48000000>;
reg = <0x0 0x1000>;
interrupts = <72>;
@@ -1108,7 +1108,7 @@ SYSC_OMAP2_SOFTRESET |
ranges = <0x0 0x22000 0x1000>;
uart1: serial@0 {
- compatible = "ti,am3352-uart", "ti,omap3-uart";
+ compatible = "ti,am3352-uart";
clock-frequency = <48000000>;
reg = <0x0 0x1000>;
interrupts = <73>;
@@ -1139,7 +1139,7 @@ SYSC_OMAP2_SOFTRESET |
ranges = <0x0 0x24000 0x1000>;
uart2: serial@0 {
- compatible = "ti,am3352-uart", "ti,omap3-uart";
+ compatible = "ti,am3352-uart";
clock-frequency = <48000000>;
reg = <0x0 0x1000>;
interrupts = <74>;
@@ -1770,7 +1770,7 @@ SYSC_OMAP2_SOFTRESET |
ranges = <0x0 0xa6000 0x1000>;
uart3: serial@0 {
- compatible = "ti,am3352-uart", "ti,omap3-uart";
+ compatible = "ti,am3352-uart";
clock-frequency = <48000000>;
reg = <0x0 0x1000>;
interrupts = <44>;
@@ -1799,7 +1799,7 @@ SYSC_OMAP2_SOFTRESET |
ranges = <0x0 0xa8000 0x1000>;
uart4: serial@0 {
- compatible = "ti,am3352-uart", "ti,omap3-uart";
+ compatible = "ti,am3352-uart";
clock-frequency = <48000000>;
reg = <0x0 0x1000>;
interrupts = <45>;
@@ -1828,7 +1828,7 @@ SYSC_OMAP2_SOFTRESET |
ranges = <0x0 0xaa000 0x1000>;
uart5: serial@0 {
- compatible = "ti,am3352-uart", "ti,omap3-uart";
+ compatible = "ti,am3352-uart";
clock-frequency = <48000000>;
reg = <0x0 0x1000>;
interrupts = <46>;
--
2.43.0
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties
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)
2025-08-27 6:05 ` Alexander Stein
2 siblings, 0 replies; 4+ messages in thread
From: Rob Herring (Arm) @ 2025-08-26 23:19 UTC (permalink / raw)
To: Alexander Stein
Cc: Krzysztof Kozlowski, devicetree, Tony Lindgren, linux-kernel,
linux-omap, Conor Dooley
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#
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties
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 ` [PATCH 1/2] ARM: dts: tps65910: Add gpio & interrupt properties Rob Herring (Arm)
@ 2025-08-27 6:05 ` Alexander Stein
2 siblings, 0 replies; 4+ messages in thread
From: Alexander Stein @ 2025-08-27 6:05 UTC (permalink / raw)
To: Tony Lindgren, Rob Herring, Krzysztof Kozlowski, Conor Dooley
Cc: linux-omap, devicetree, linux-kernel
Am Dienstag, 26. August 2025, 15:42:57 CEST schrieb Alexander Stein:
> 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(+)
>
> diff --git a/arch/arm/boot/dts/tps65910.dtsi b/arch/arm/boot/dts/tps65910.dtsi
> index a941d1e623280..161ce31085d1e 100644
> --- a/arch/arm/boot/dts/tps65910.dtsi
> +++ b/arch/arm/boot/dts/tps65910.dtsi
> @@ -10,6 +10,10 @@
>
> &tps {
> compatible = "ti,tps65910";
> + interrupt-controller;
> + #interrupt-cells = <1>;
Meh, this should obviously be <2>. Will fix in v2.
Best regards,
Alexander
> + gpio-controller;
> + #gpio-cells = <2>;
>
> regulators {
> #address-cells = <1>;
>
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
^ permalink raw reply [flat|nested] 4+ messages in thread