From: Akhila YS <akhilayalmati@gmail.com>
To: 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>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Akhila YS <akhilayalmati@gmail.com>
Subject: [PATCH 0/5] dt-bindings: Microchip/Atmel AT91/SAMA system peripherals: convert to YAML
Date: Tue, 17 Feb 2026 17:24:18 +0000 [thread overview]
Message-ID: <20260217-arm-microchip-v1-0-ae5d907e10e3@gmail.com> (raw)
Convert various legacy .txt bindings for Microchip (formerly Atmel) AT91/SAMA
family system peripherals to proper YAML schemas. This includes:
- CHIPID (SoC ID register block)
- PIT (Period Interval Timer, old style)
- PIT64B (64-bit Period Interval Timer, newer parts)
- ST (System Timer, including watchdog subnode)
- RAMC/SDRAMC/DDRAMC/UDDRC (SDRAM/DDR memory controller
Signed-off-by: Akhila YS <akhilayalmati@gmail.com>
---
Akhila YS (5):
dt-bindings: arm: microchip,sama7g5-chipid : convert to DT schema
dt-bindings: arm: atmel,at91sam9260-pit: convert to DT schema
dt-bindings: arm: microchip,sam9x60-pit64b : convert to DT schema
dt-bindings: arm: atmel,at91rm9200-st: convert to DT schema
dt-bindings: arm: atmel,at91rm9200-sdramc: convert to DT schema
.../bindings/arm/atmel,at91rm9200-sdramc.yaml | 67 ++++++++++++++++++++
.../bindings/arm/atmel,at91rm9200-st.yaml | 65 ++++++++++++++++++++
.../bindings/arm/atmel,at91sam9260-pit.yaml | 49 +++++++++++++++
.../devicetree/bindings/arm/atmel-sysregs.txt | 48 ---------------
.../bindings/arm/microchip,sam9x60-pit64b.yaml | 71 ++++++++++++++++++++++
.../bindings/arm/microchip,sama7g5-chipid.yaml | 41 +++++++++++++
6 files changed, 293 insertions(+), 48 deletions(-)
---
base-commit: ca3a02fda4da8e2c1cb6baee5d72352e9e2cfaea
change-id: 20260128-arm-microchip-c0c0515024e6
Best regards,
--
Akhila YS <akhilayalmati@gmail.com>
next reply other threads:[~2026-02-17 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 17:24 Akhila YS [this message]
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
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=20260217-arm-microchip-v1-0-ae5d907e10e3@gmail.com \
--to=akhilayalmati@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@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