mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akhila YS <akhilayalmati@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/5] dt-bindings: arm: microchip,sam9x60-pit64b : convert to DT schema
Date: Tue, 24 Feb 2026 20:14:45 +0530	[thread overview]
Message-ID: <4b16c937-6195-4307-88d2-874052203543@gmail.com> (raw)
In-Reply-To: <20260217-surgical-gently-7f58e6fb5e5e@spud>


On 17-02-2026 23:23, Conor Dooley wrote:
> On Tue, Feb 17, 2026 at 05:24:21PM +0000, Akhila YS wrote:
>> Convert Atmel Periodic interval timer of 64bit (PIT64b) binding to YAML
>> format.
>> Changes during conversion:
>> - Add missing compatible "microchip,sama7g5-pit64b" along with a fallback
>> compatible "microchip,sam9x60-pit64b".
>>
>> Signed-off-by: Akhila YS <akhilayalmati@gmail.com>
>> ---
>>  .../bindings/arm/microchip,sam9x60-pit64b.yaml     | 71 ++++++++++++++++++++++
>>  1 file changed, 71 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/microchip,sam9x60-pit64b.yaml b/Documentation/devicetree/bindings/arm/microchip,sam9x60-pit64b.yaml
>> new file mode 100644
>> index 000000000000..6bf8e81d4c72
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/microchip,sam9x60-pit64b.yaml
>> @@ -0,0 +1,71 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/arm/microchip,sam9x60-pit64b.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Microchip PIT64B 64-bit Periodic Interval Timer
>> +
>> +maintainers:
>> +  - Nicolas Ferre <nicolas.ferre@microchip.com>
>> +  - Claudiu Beznea <claudiu.beznea@microchip.com>
>> +
>> +description:
>> +  The Microchip PIT64B is a 64-bit periodic interval timer used in
>> +  several modern Microchip ARM SoCs including SAM9X60, SAM9X7 and
>> +  SAMA7D65 families. It provides extended timing range, flexible
>> +  clock selection and supports both periodic and one-shot interrupt
>> +  generation modes.
>> +
>> +properties:
>> +  compatible:
>> +    oneOf:
>> +      - const: microchip,sam9x60-pit64b
>> +      - items:
>> +          - const: microchip,sama7d65-pit64b
>> +          - const: microchip,sam9x60-pit64b
>> +      - items:
>> +          - const: microchip,sama7g5-pit64b
>> +          - const: microchip,sam9x60-pit64b
>> +      - items:
>> +          - const: microchip,sam9x7-pit64b
>> +          - const: microchip,sam9x60-pit64b
> These three can be merged into one enum + const items list.


Okay.

>
>> +  reg:
>> +    maxItems: 1
>> +
>> +  interrupts:
>> +    maxItems: 1
>> +
>> +  clocks:
>> +    minItems: 1
>> +    maxItems: 2
>> +
>> +  clock-names:
>> +    oneOf:
>> +      - const: pclk
>> +      - items:
>> +          - const: pclk
>> +          - const: gclk
> This can be an items list with minItems: 1, but there should be some
> conditional logic used to permit gclk only where it is valid. The text
> binding removal is missing so I cannot say exactly what that logic
> should be.


Okay.

>
> pw-bot: changes-requested
>
> Cheers,
> Conor.
>
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +  - interrupts
>> +  - clocks
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> +  - |
>> +    #include <dt-bindings/interrupt-controller/irq.h>
>> +    #include <dt-bindings/clock/at91.h>
>> +    timer@f0028000 {
>> +        compatible = "microchip,sama7g5-pit64b", "microchip,sam9x60-pit64b";
>> +        reg = <0xf0028000 0x100>;
>> +        interrupts = <37 IRQ_TYPE_LEVEL_HIGH 7>;
>> +        clocks = <&pmc PMC_TYPE_PERIPHERAL 37>, <&pmc PMC_TYPE_GCK 37>;
>> +        clock-names = "pclk", "gclk";
>> +    };
>> +...
>>
>> -- 
>> 2.43.0
>>
-- 
Best Regards,
Akhila.


  reply	other threads:[~2026-02-24 14:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 17:24 [PATCH 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Akhila YS
2026-02-17 17:24 ` [PATCH 1/5] dt-bindings: arm: microchip,sama7g5-chipid : convert to DT schema Akhila YS
2026-02-17 17:51   ` Conor Dooley
2026-02-24 14:43     ` Akhila YS
2026-02-17 17:24 ` [PATCH 2/5] dt-bindings: arm: atmel,at91sam9260-pit: " Akhila YS
2026-02-17 17:24 ` [PATCH 3/5] dt-bindings: arm: microchip,sam9x60-pit64b : " Akhila YS
2026-02-17 17:53   ` Conor Dooley
2026-02-24 14:44     ` Akhila YS [this message]
2026-02-17 17:24 ` [PATCH 4/5] dt-bindings: arm: atmel,at91rm9200-st: " Akhila YS
2026-02-17 17:24 ` [PATCH 5/5] dt-bindings: arm: atmel,at91rm9200-sdramc: " Akhila YS
2026-02-17 17:51 ` [PATCH 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Conor Dooley
2026-02-24 14:42   ` Akhila YS
2026-02-24 14:56     ` Conor Dooley

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=4b16c937-6195-4307-88d2-874052203543@gmail.com \
    --to=akhilayalmati@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh@kernel.org \
    /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

all inboxes | Powered by JetHome®