The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Akhila YS <akhilayalmati@gmail.com>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 3/5] dt-bindings: arm: microchip,sam9x60-pit64b : convert to DT schema
Date: Sat, 7 Mar 2026 21:16:39 +0530	[thread overview]
Message-ID: <2185210c-d407-4019-a364-9e72df93029a@gmail.com> (raw)
In-Reply-To: <aacb74f1-5d4a-4ed1-92fe-0c5536691274@tuxon.dev>


On 07-03-2026 20:01, Claudiu Beznea wrote:
>
>
> On 2/27/26 17:14, 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".
>>
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>> Signed-off-by: Akhila YS <akhilayalmati@gmail.com>
>> ---
>>   .../devicetree/bindings/arm/atmel-sysregs.txt      |  8 ---
>>   .../bindings/arm/microchip,sam9x60-pit64b.yaml     | 68
>> ++++++++++++++++++++++
>>   2 files changed, 68 insertions(+), 8 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> index 70059f66f2b4..d0561f7f465c 100644
>> --- a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> +++ b/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
>> @@ -1,13 +1,5 @@
>>   Atmel system registers
>>   -PIT64B Timer required properties:
>> -- compatible: Should be "microchip,sam9x60-pit64b" or
>> -            "microchip,sam9x7-pit64b", "microchip,sam9x60-pit64b"
>> -            "microchip,sama7d65-pit64b", "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/arm/microchip,sam9x60-pit64b.yaml
>> b/Documentation/devicetree/bindings/arm/microchip,sam9x60-pit64b.yaml
>> new file mode 100644
>> index 000000000000..f00ac7e858d9
>> --- /dev/null
>> +++
>> b/Documentation/devicetree/bindings/arm/microchip,sam9x60-pit64b.yaml
>> @@ -0,0 +1,68 @@
>> +# 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@tuxon.dev>
>> +
>> +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:
>> +          - enum:
>> +              - microchip,sama7d65-pit64b
>> +              - microchip,sama7g5-pit64b
>> +              - microchip,sam9x7-pit64b
>
> Same here, I'll adjust this list to be alphanumerically sorted, thus,
> microchip,sam9x7-pit64b first. Other than that: 


Thank you claudiu.

>
> Reviewed-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
>
-- 
Best Regards,
Akhila.


  reply	other threads:[~2026-03-07 15:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 15:14 [PATCH v4 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Akhila YS
2026-02-27 15:14 ` [PATCH v4 1/5] dt-bindings: arm: microchip,sama7g5-chipid : convert to DT schema Akhila YS
2026-03-07 14:30   ` Claudiu Beznea
2026-03-07 15:45     ` Akhila YS
2026-02-27 15:14 ` [PATCH v4 2/5] dt-bindings: arm: atmel,at91sam9260-pit: " Akhila YS
2026-03-07 14:30   ` Claudiu Beznea
2026-02-27 15:14 ` [PATCH v4 3/5] dt-bindings: arm: microchip,sam9x60-pit64b : " Akhila YS
2026-03-07 14:31   ` Claudiu Beznea
2026-03-07 15:46     ` Akhila YS [this message]
2026-02-27 15:14 ` [PATCH v4 4/5] dt-bindings: arm: atmel,at91rm9200-st: " Akhila YS
2026-03-07 14:31   ` Claudiu Beznea
2026-02-27 15:14 ` [PATCH v4 5/5] dt-bindings: arm: atmel,at91rm9200-sdramc: " Akhila YS
2026-02-27 17:34   ` Conor Dooley
2026-03-07 14:34   ` Claudiu Beznea
2026-03-08 16:08 ` [PATCH v4 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML Claudiu Beznea

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=2185210c-d407-4019-a364-9e72df93029a@gmail.com \
    --to=akhilayalmati@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --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