From: Sergiu Moga <sergiu.moga@microchip.com>
To: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski@canonical.com>,
<nicolas.ferre@microchip.com>, <claudiu.beznea@microchip.com>
Cc: <linux-rtc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Sergiu Moga <sergiu.moga@microchip.com>
Subject: [PATCH v2 0/5] dt-bindings: rtc: convert at91sam9 bindings to
Date: Thu, 3 Mar 2022 16:06:21 +0200 [thread overview]
Message-ID: <20220303140626.38129-1-sergiu.moga@microchip.com> (raw)
This patch series addresses the conversion of the RTC binding for
Atmel/Microchip SoCs to Device Tree Schema format. It also changes
the node names from some of the "dtsi" files from "rtt" to the more
generic "rtc", while moving some of the specific properties from the
"dts" files to the "dtsi" files as well as adding this required property to
the "dtsi" files that were missing it.
Changes since v1:
- Add the "start-year" property as suggested by Alexandre Belloni
- Fix the errors generated from not using the more generic "rtc" node
name for the example of the binding, as suggested by Krzysztof Kozlowski
- Replace the "uint32-array" type of the "atmel,rtt-rtc-time-reg"
property with "syscon", as suggested by Krzysztof Kozlowski
- Move the "atmel,rtt-rtc-time-reg" property from some of the
Atmel/Microchip board files to the SoC files
- Add the "atmel,rtt-rtc-time-reg" required property to the
Atmel/Microchip SoC files that were missing it
- Use the more generic "rtc" node name inside the Atmel/Microchip SoC
files that were using "rtt" instead
- Add SAMA7G5 compatible strings list to the DT binding
Sergiu Moga (5):
ARM: dts: at91: Move rtt node properties from "dts" file to "dtsi"
file
ARM: dts: at91: Add the required `atmel,rtt-rtc-time-reg` property
ARM: dts: at91: Use the generic "rtc" node name for the rtt IPs
dt-bindings: rtc: convert at91sam9 bindings to json-schema
dt-bindings: rtc: at91: Add SAMA7G5 compatible strings list
.../bindings/rtc/atmel,at91sam9-rtc.txt | 25 -------
.../bindings/rtc/atmel,at91sam9-rtc.yaml | 65 +++++++++++++++++++
arch/arm/boot/dts/at91-sam9x60ek.dts | 5 --
arch/arm/boot/dts/at91-sama7g5ek.dts | 4 --
arch/arm/boot/dts/at91sam9260.dtsi | 1 +
arch/arm/boot/dts/at91sam9260ek.dts | 1 -
arch/arm/boot/dts/at91sam9261.dtsi | 1 +
arch/arm/boot/dts/at91sam9263.dtsi | 2 +
arch/arm/boot/dts/at91sam9g45.dtsi | 1 +
arch/arm/boot/dts/at91sam9m10g45ek.dts | 1 -
arch/arm/boot/dts/at91sam9rl.dtsi | 1 +
arch/arm/boot/dts/sam9x60.dtsi | 3 +-
arch/arm/boot/dts/sama7g5.dtsi | 3 +-
13 files changed, 75 insertions(+), 38 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/rtc/atmel,at91sam9-rtc.txt
create mode 100644 Documentation/devicetree/bindings/rtc/atmel,at91sam9-rtc.yaml
--
2.25.1
next reply other threads:[~2022-03-03 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 14:06 Sergiu Moga [this message]
2022-03-03 14:06 ` [PATCH v2 1/5] ARM: dts: at91: Move rtt node properties from "dts" file to "dtsi" file Sergiu Moga
2022-03-03 16:07 ` Alexandre Belloni
2022-03-04 13:10 ` Sergiu.Moga
2022-03-03 14:06 ` [PATCH v2 2/5] ARM: dts: at91: Add the required `atmel,rtt-rtc-time-reg` property Sergiu Moga
2022-03-04 11:06 ` [PATCH v2 2/5] ARM: dts: at91: Add the required `atmel, rtt-rtc-time-reg` property Tudor.Ambarus
2022-03-03 14:06 ` [PATCH v2 3/5] ARM: dts: at91: Use the generic "rtc" node name for the rtt IPs Sergiu Moga
2022-03-03 14:47 ` Krzysztof Kozlowski
2022-03-04 11:13 ` Tudor.Ambarus
2022-03-03 14:06 ` [PATCH v2 4/5] dt-bindings: rtc: convert at91sam9 bindings to json-schema Sergiu Moga
2022-03-03 14:21 ` Krzysztof Kozlowski
2022-03-04 13:17 ` Sergiu.Moga
2022-03-03 14:06 ` [PATCH v2 5/5] dt-bindings: rtc: at91: Add SAMA7G5 compatible strings list Sergiu Moga
2022-03-03 14:48 ` Krzysztof Kozlowski
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=20220303140626.38129-1-sergiu.moga@microchip.com \
--to=sergiu.moga@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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