[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46eced08-5bf6-3e4b-7a91-ff4d16c7dab9@linaro.org>
Date: Wed, 31 May 2023 10:55:50 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Claudiu Beznea <claudiu.beznea@...rochip.com>, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com,
daniel.lezcano@...aro.org, tglx@...utronix.de,
wim@...ux-watchdog.org, linux@...ck-us.net
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-watchdog@...r.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: timer: atmel,at91sam9260-pit: convert
to yaml
On 30/05/2023 11:07, Claudiu Beznea wrote:
> Convert Microchip AT91 PIT bindings to YAML. Along with it clocks and
> clock-names bindings were added as the drivers needs it to ensure proper
> hardware functionality.
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea@...rochip.com>
> ---
> .../devicetree/bindings/arm/atmel-sysregs.txt | 12 ---
> .../bindings/timer/atmel,at91sam9260-pit.yaml | 99 +++++++++++++++++++
> 2 files changed, 99 insertions(+), 12 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/timer/atmel,at91sam9260-pit.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
> index 67a66bf74895..54d3f586403e 100644
> --- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
> +++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
> @@ -4,18 +4,6 @@ Chipid required properties:
> - compatible: Should be "atmel,sama5d2-chipid" or "microchip,sama7g5-chipid"
> - reg : Should contain registers location and length
>
> -PIT Timer required properties:
> -- compatible: Should be "atmel,at91sam9260-pit"
> -- reg: Should contain registers location and length
> -- interrupts: Should contain interrupt for the PIT which is the IRQ line
> - shared across all System Controller members.
> -
> -PIT64B Timer required properties:
> -- compatible: Should be "microchip,sam9x60-pit64b"
> -- reg: Should contain registers location and length
> -- interrupts: Should contain interrupt for PIT64B timer
> -- clocks: Should contain the available clock sources for PIT64B timer.
> -
> System Timer (ST) required properties:
> - compatible: Should be "atmel,at91rm9200-st", "syscon", "simple-mfd"
> - reg: Should contain registers location and length
> diff --git a/Documentation/devicetree/bindings/timer/atmel,at91sam9260-pit.yaml b/Documentation/devicetree/bindings/timer/atmel,at91sam9260-pit.yaml
> new file mode 100644
> index 000000000000..d0f3f80db4cb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/timer/atmel,at91sam9260-pit.yaml
> @@ -0,0 +1,99 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/timer/atmel,at91sam9260-pit.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Microchip AT91 Periodic Interval Timer (PIT)
> +
> +maintainers:
> + - Claudiu Beznea <claudiu.beznea@...rochip.com>
> +
> +description:
> + Microchip AT91 periodic interval timer provides the operating system scheduler
> + interrupt. It is designed to offer maximum accuracy and efficient management,
> + even for systems with long response time.
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - const: microchip,sama7g5-pit64b
>From where do you have this compatible? Wasn't in old binding and commit
msg does not explain it.
> + - const: microchip,sam9x60-pit64b
> + - items:
> + enum:
These are not items. Just enum.. Does it even work?
> + - atmel,at91sam9260-pit
> + - microchip,sam9x60-pit64b
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + minItems: 1
> + maxItems: 2
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> +
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: atmel,at91sam9260-pit
> + then:
> + properties:
> + interrupts:
> + description:
> + Shared interrupt between all system controller members (power management
> + controller, watchdog, PIT, reset controller, real-time timer, real-time
> + clock, memory controller, debug unit, system timer).
> + clocks:
> + maxItems: 1
> +
> + else:
> + properties:
> + clocks:
> + minItems: 2
> + clock-names:
> + items:
> + - const: pclk
> + - const: gclk
interrupts? They are still required, so why no description here?
> + required:
> + - clock-names
> +
> +unevaluatedProperties: false
additionalProperties:false instead
> +
Best regards,
Krzysztof
Powered by blists - more mailing lists