Skip to contentSkip to conversation

dt-bindings: timer: Update TI timer to yaml and add compatible for am6

PATCH In review Tony Lindgren 4 participants 8 messages Apr 8, 2022 – Apr 11, 2022

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 dt-bindings: timer: Update TI timer to yaml and add compatible for am6

Let's update the TI timer binding to use yaml. And add compatible for ti,am654-timer for TI am64, am65 and j72 SoCs. As the timer hardware is the same between am64, am65 and j72 we use the compatible name for the earliest SoC with this timer.

As this binding is specific to the TI dual-mode timers also known as dm-timers, let's use ti,timer-dm.yaml naming for the new file.

Cc Daniel Lezcano <[email protected]>
Cc Keerthy <[email protected]>
Cc Nishanth Menon <[email protected]>
Cc Vignesh Raghavendra <[email protected]>
---
 .../bindings/timer/ti,timer-dm.yaml           | 105 ++++++++++++++++++
 .../devicetree/bindings/timer/ti,timer.txt    |  44 --------
 2 files changed, 105 insertions(+), 44 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/timer/ti,timer-dm.yaml
 delete mode 100644 Documentation/devicetree/bindings/timer/ti,timer.txt
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +105 -0
new file mode 100644
@@ -0,0 +1,105 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/timer/ti,timer-dm.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Binding for TI dual-mode timer
+
+maintainers:
+  - Tony Lindgren <[email protected]>
+
+description: |
+  The TI dual-mode timer is a general purpose timer with PWM capabilities.
+
+properties:
+  compatible:
+    enum:
+      - ti,omap2420-timer
+      - ti,omap3430-timer
+      - ti,omap4430-timer
+      - ti,omap5430-timer
+      - ti,am335x-timer
+      - ti,am335x-timer-1ms
+      - ti,am654-timer
+
+  reg:
+    minItems: 1
+    maxItems: 2
+    description: Timer IO register range
+
+  '#address-cells':
+    enum: [ 1, 2 ]
+
+  '#size-cells':
+    enum: [ 1, 2 ]
+
+  clocks:
+    description:
+      The functional clock for the timer. Some SoCs like omap24xx also have a
+      separate interface clock, and some clocks may be only defined for the
+      interconnect target module parent.
+    minItems: 1
+    maxItems: 2
+
+  clock-names:
+    description:
+      Timer clock names like "fck", "timer_sys_ck".
+    oneOf:
+      - enum: [ ick, fck ]
+      - items:
+          - const: fck
+          - enum: [ ick, timer_sys_ck ]
+
+  interrupts:
+    description:
+      Interrupt if available. The timer PWM features may be usable
+      in a limited way even without interrupts.
+    maxItems: 1
+
+  ti,timer-alwon:
+    description:
+      Timer is always enabled when the SoC is powered. Note that some SoCs like
+      am335x can suspend to PM coprocessor RTC only mode and in that case the
+      SoC power is cut including timers.
+    type: boolean
+
+  ti,timer-dsp:
+    description:
+      Timer is routable to the DSP in addition to the operating system.
+    type: boolean
+
+  ti,timer-pwm:
+    description:
+      Timer has been wired for PWM capability.
+    type: boolean
+
+  ti,timer-secure:
+    description:
+      Timer access has been limited to secure mode only.
+    type: boolean
+
+  ti,hwmods:
+    description:
+      Name of the HWMOD associated with timer. This is for legacy
+      omap2/3 platforms only.
+    $ref: /schemas/types.yaml#/definitions/string
+    deprecated: true
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+examples:
+  - |
+    timer1: timer@0 {
+      compatible = "ti,am335x-timer-1ms";
+      reg = <0x0 0x400>;
+      interrupts = <67>;
+      ti,timer-alwon;
+      clocks = <&timer1_fck>;
+      clock-names = "fck";
+    };
+...
Documentation/devicetree/bindings/timer/ti,timer.txt deleted +0 -44

44 lines not on this page · raw message

Signature · 1 line
2.35.1
#1 lore raw

On 11:12-20220408, Tony Lindgren wrote:
[...]

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 94

Quoted 13 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +13 -0
+  ti,hwmods:
+    description:
+      Name of the HWMOD associated with timer. This is for legacy
+      omap2/3 platforms only.
+    $ref: /schemas/types.yaml#/definitions/string
+    deprecated: true
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+

Should we strengthen the check like in 8250_omap.yaml - something to the effect of:

if:
properties:
compatible:
contains:
enum:
- ti,omap2420-timer
- ti,omap3430-timer
- ti,omap4430-timer

then:
properties:
ti,hwmods:
items:
- pattern: "^timer([1-9]+)$"

else:
properties:
ti,hwmods: false

Signature · 3 lines
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
#2 lore raw
Quoted 35 lines · Nishanth Menon

On 11:12-20220408, Tony Lindgren wrote:
[...]

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 94

Quoted 13 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +13 -0
+  ti,hwmods:
+    description:
+      Name of the HWMOD associated with timer. This is for legacy
+      omap2/3 platforms only.
+    $ref: /schemas/types.yaml#/definitions/string
+    deprecated: true
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+

Should we strengthen the check like in 8250_omap.yaml - something to the effect of:

if:
properties:
compatible:
contains:
enum:
- ti,omap2420-timer
- ti,omap3430-timer
- ti,omap4430-timer

then:
properties:
ti,hwmods:
items:
- pattern: "^timer([1-9]+)$"

Quoted 3 lines

else:
properties:
ti,hwmods: false

Sure, sounds good to me. I need to check again what all SoCs are already using ti-sysc for all the timers. I believe system timers only got updated for some SoCs.

Regards,

Tony

#3 lore raw
In reply to Nishanth Menon
Quoted 20 lines · Nishanth Menon

On 11:12-20220408, Tony Lindgren wrote:
[...]

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 94

Quoted 13 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +13 -0
+  ti,hwmods:
+    description:
+      Name of the HWMOD associated with timer. This is for legacy
+      omap2/3 platforms only.
+    $ref: /schemas/types.yaml#/definitions/string
+    deprecated: true
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+

Should we strengthen the check like in 8250_omap.yaml - something to the effect of:

Quoted 1 line

if:

Yes, please. Within allOf because other properties also might need such constraints.

Best regards,
Krzysztof

#4 lore raw
In reply to Tony Lindgren
Quoted 7 lines · Tony Lindgren

Let's update the TI timer binding to use yaml. And add compatible for ti,am654-timer for TI am64, am65 and j72 SoCs. As the timer hardware is the same between am64, am65 and j72 we use the compatible name for the earliest SoC with this timer.

As this binding is specific to the TI dual-mode timers also known as dm-timers, let's use ti,timer-dm.yaml naming for the new file.

Thank you for your patch. There is something to discuss/improve.

Quoted 3 lines
---
 .../bindings/timer/ti,timer-dm.yaml           | 105 ++++++++++++++++++
 .../devicetree/bindings/timer/ti,timer.txt    |  44 --------

pwm-omap-dmtimer.txt references old path.

Quoted 9 lines
 2 files changed, 105 insertions(+), 44 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/timer/ti,timer-dm.yaml
 delete mode 100644 Documentation/devicetree/bindings/timer/ti,timer.txt
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +0 -0
new file mode 100644

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 7

Quoted 7 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +7 -0
@@ -0,0 +1,105 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/timer/ti,timer-dm.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Binding for TI dual-mode timer

"TI dual-mode timer"

Quoted 7 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +7 -0
+
+maintainers:
+  - Tony Lindgren <[email protected]>
+
+description: |
+  The TI dual-mode timer is a general purpose timer with PWM capabilities.
+

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 24

Quoted 10 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +10 -0
+properties:
+  compatible:
+    enum:
+      - ti,omap2420-timer
+      - ti,omap3430-timer
+      - ti,omap4430-timer
+      - ti,omap5430-timer
+      - ti,am335x-timer
+      - ti,am335x-timer-1ms
+      - ti,am654-timer

How about ordering the entries by name (so amxxx before omapxxx)?

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 29

Quoted 5 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +5 -0
+
+  reg:
+    minItems: 1
+    maxItems: 2
+    description: Timer IO register range

This was maxItems:1 in old binding, so please mention briefly in commit msg why the change is needed. If only some versions need it, then add allOf:if:then: constraints.

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 35

Quoted 6 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +6 -0
+
+  '#address-cells':
+    enum: [ 1, 2 ]
+
+  '#size-cells':
+    enum: [ 1, 2 ]

The same. Are these changes to the binding an effect of new compatible? If yes, better to split it into two patches. One for old binding (passing dtbs_check on old compatibles) and one for new compatible with new properties.

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 43

Quoted 8 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +8 -0
+
+  clocks:
+    description:
+      The functional clock for the timer. Some SoCs like omap24xx also have a
+      separate interface clock, and some clocks may be only defined for the
+      interconnect target module parent.
+    minItems: 1
+    maxItems: 2

The same - not mentioned in commit msg.

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 52

Quoted 9 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +9 -0
+
+  clock-names:
+    description:
+      Timer clock names like "fck", "timer_sys_ck".
+    oneOf:
+      - enum: [ ick, fck ]
+      - items:
+          - const: fck
+          - enum: [ ick, timer_sys_ck ]

Are the combinations depending on compatible? If so, you need allOf:if:then:

Quoted 29 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +29 -0
+
+  interrupts:
+    description:
+      Interrupt if available. The timer PWM features may be usable
+      in a limited way even without interrupts.
+    maxItems: 1
+
+  ti,timer-alwon:
+    description:
+      Timer is always enabled when the SoC is powered. Note that some SoCs like
+      am335x can suspend to PM coprocessor RTC only mode and in that case the
+      SoC power is cut including timers.
+    type: boolean
+
+  ti,timer-dsp:
+    description:
+      Timer is routable to the DSP in addition to the operating system.
+    type: boolean
+
+  ti,timer-pwm:
+    description:
+      Timer has been wired for PWM capability.
+    type: boolean
+
+  ti,timer-secure:
+    description:
+      Timer access has been limited to secure mode only.
+    type: boolean
+

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 91

Quoted 10 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +10 -0
+  ti,hwmods:
+    description:
+      Name of the HWMOD associated with timer. This is for legacy
+      omap2/3 platforms only.
+    $ref: /schemas/types.yaml#/definitions/string
+    deprecated: true
+
+required:
+  - compatible
+  - reg

Missing interrupts - they were required. Aren't anymore?

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 94

Quoted 3 lines
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +3 -0
+
+additionalProperties: false
+

Best regards,
Krzysztof

#5 lore raw
Quoted 6 lines · Krzysztof Kozlowski

Documentation/devicetree/bindings/timer/ti,timer-dm.yaml line 91

Quoted 3 lines · Tony Lindgren
Documentation/devicetree/bindings/timer/ti,timer-dm.yaml new file +3 -0
+required:
+  - compatible
+  - reg

Missing interrupts - they were required. Aren't anymore?

There are cases where the interrupts are not routable to Linux yet the timer registers can be accessible. These timers can still be usable in a limited way for some PWM cases though.

Thanks for the good comments on the binding, will update accordingly. Yeah adding a second patch for the new features makes sense as few things have changed with the new SoCs.

Regards,

Tony

maintainer
#6 lore raw
In reply to Tony Lindgren
Quoted 13 lines · Tony Lindgren

Let's update the TI timer binding to use yaml. And add compatible for ti,am654-timer for TI am64, am65 and j72 SoCs. As the timer hardware is the same between am64, am65 and j72 we use the compatible name for the earliest SoC with this timer.

As this binding is specific to the TI dual-mode timers also known as dm-timers, let's use ti,timer-dm.yaml naming for the new file.

Cc Daniel Lezcano <[email protected]>
Cc Keerthy <[email protected]>
Cc Nishanth Menon <[email protected]>
Cc Vignesh Raghavendra <[email protected]>
Quoted 7 lines
---
 .../bindings/timer/ti,timer-dm.yaml           | 105 ++++++++++++++++++
 .../devicetree/bindings/timer/ti,timer.txt    |  44 --------
 2 files changed, 105 insertions(+), 44 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/timer/ti,timer-dm.yaml
 delete mode 100644 Documentation/devicetree/bindings/timer/ti,timer.txt

Running 'make dtbs_check' with the schema in this patch gives the following warnings. Consider if they are expected or the schema is incorrect. These may not be new warnings.

Note that it is not yet a requirement to have 0 warnings for dtbs_check. This will change in the future.

Full log is available here: https://patchwork.ozlabs.org/patch/

timer@0: compatible:0: 'ti,am4372-timer-1ms' is not one of ['ti,omap2420-timer', 'ti,omap3430-timer', 'ti,omap4430-timer', 'ti,omap5430-timer', 'ti,am335x-timer', 'ti,am335x-timer-1ms', 'ti,am654-timer']

	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb

timer@0: compatible:0: 'ti,am4372-timer' is not one of ['ti,omap2420-timer', 'ti,omap3430-timer', 'ti,omap4430-timer', 'ti,omap5430-timer', 'ti,am335x-timer', 'ti,am335x-timer-1ms', 'ti,am654-timer']

	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb

timer@0: compatible: ['ti,am4372-timer-1ms', 'ti,am335x-timer-1ms'] is too long

	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb

timer@0: compatible: ['ti,am4372-timer', 'ti,am335x-timer'] is too long

	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-cm-t43.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-gp-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-idk-evm.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sbc-t43.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am437x-sk-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
	arch/arm/boot/dts/am43x-epos-evm.dtb
#7 lore raw
Quoted 22 lines · Rob Herring
Quoted 13 lines · Tony Lindgren

Let's update the TI timer binding to use yaml. And add compatible for ti,am654-timer for TI am64, am65 and j72 SoCs. As the timer hardware is the same between am64, am65 and j72 we use the compatible name for the earliest SoC with this timer.

As this binding is specific to the TI dual-mode timers also known as dm-timers, let's use ti,timer-dm.yaml naming for the new file.

Cc Daniel Lezcano <[email protected]>
Cc Keerthy <[email protected]>
Cc Nishanth Menon <[email protected]>
Cc Vignesh Raghavendra <[email protected]>
Quoted 7 lines
---
 .../bindings/timer/ti,timer-dm.yaml           | 105 ++++++++++++++++++
 .../devicetree/bindings/timer/ti,timer.txt    |  44 --------
 2 files changed, 105 insertions(+), 44 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/timer/ti,timer-dm.yaml
 delete mode 100644 Documentation/devicetree/bindings/timer/ti,timer.txt
Quoted 3 lines

Running 'make dtbs_check' with the schema in this patch gives the following warnings. Consider if they are expected or the schema is incorrect. These may not be new warnings.

Well I was planning to drop the unused ti,am4372-timer related properties, but instead will document those as discussed in the related dts thread. I'll be sending an updated version a bit later on.

Regards,

Tony