From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3 0/4] rtc: convert multiple bindings into dtschema
Date: Sat, 13 Apr 2024 20:22:51 -0000 [thread overview]
Message-ID: <20240413-rtc_dtschema-v3-0-eff368bcc471@gmail.com> (raw)
This series converts the following bindings into dtschema, moving them
to trivial-rtc whenever possible:
- google,goldfish-rtc: trivial-rtc, referenced in mips arch.
- lpc32xx-rtc: trivial-rtc, referenced in arm arch.
- maxim,ds1742: trivial-rtc, not referenced in arch, cheap conversion.
- orion-rtc: trival-rtc, referenced in arm arch.
- pxa-rtc: add missing properties and convert. Referenced in arm arch.
- rtc-aspeed: 3 devices to trivial-rtc, all referenced in arm arch.
- st,spear600-rtc: trivial-rtc, referenced in arm arch.
- stmp3xxx-rtc: add compatibles and convert, referenced in arm arch.
- via,vt8500-rtc: trivial-rtc, referenced in arm arch.
The only reference to the lpc32xx RTC makes use of a 'clocks' property
that does not describe a controllable signal (it is in fact a fixed
32768 Hz crystal, the input clock of the SoC). Remove this property to
better describe the device and avoid errors when checking the dts
against the RTC binding.
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
Changes in v3:
- Fix typo in commit description (rtc-aspeed).
- Move lpc32xx-rtc to trivial-rtc again.
- Remove 'clocks' property from the rtc node in lpc32xx.dtsi.
- Link to v2: https://lore.kernel.org/r/20240410-rtc_dtschema-v2-0-d32a11ab0745 at gmail.com
Changes in v2:
- General: squash all moves to trivial-rtc into a single patch.
- MAINTAINERS: remove reference to google,goldfish-rtc.txt
- lpc32xx-rtc: create own binding to add the undocumented 'clocks'
property.
- fsl,stmp3xxx-rtc.yaml: document missing compatibles.
- Link to v1: https://lore.kernel.org/r/20240408-rtc_dtschema-v1-0-c447542fc362 at gmail.com
---
Javier Carrasco (4):
arm: dts: nxp: lpc: lpc32xx: drop 'clocks' form rtc
dt-bindings: rtc: convert trivial devices into dtschema
dt-bindings: rtc: pxa-rtc: convert to dtschema
dt-bindings: rtc: stmp3xxx-rtc: convert to dtschema
.../devicetree/bindings/rtc/fsl,stmp3xxx-rtc.yaml | 51 ++++++++++++++++++++++
.../bindings/rtc/google,goldfish-rtc.txt | 17 --------
.../devicetree/bindings/rtc/lpc32xx-rtc.txt | 15 -------
.../devicetree/bindings/rtc/marvell,pxa-rtc.yaml | 40 +++++++++++++++++
.../devicetree/bindings/rtc/maxim,ds1742.txt | 12 -----
.../devicetree/bindings/rtc/orion-rtc.txt | 18 --------
Documentation/devicetree/bindings/rtc/pxa-rtc.txt | 14 ------
.../devicetree/bindings/rtc/rtc-aspeed.txt | 22 ----------
.../devicetree/bindings/rtc/spear-rtc.txt | 15 -------
.../devicetree/bindings/rtc/stmp3xxx-rtc.txt | 21 ---------
.../devicetree/bindings/rtc/trivial-rtc.yaml | 18 ++++++++
.../devicetree/bindings/rtc/via,vt8500-rtc.txt | 15 -------
MAINTAINERS | 1 -
arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi | 1 -
14 files changed, 109 insertions(+), 151 deletions(-)
---
base-commit: fec50db7033ea478773b159e0e2efb135270e3b7
change-id: 20240406-rtc_dtschema-302824d1ec20
Best regards,
--
Javier Carrasco <javier.carrasco.cruz@gmail.com>
next reply other threads:[~2024-04-13 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 20:22 Javier Carrasco [this message]
2024-04-13 20:22 ` [PATCH v3 1/4] arm: dts: nxp: lpc: lpc32xx: drop 'clocks' form rtc Javier Carrasco
2024-06-03 10:24 ` Javier Carrasco
2024-04-13 20:22 ` [PATCH v3 3/4] dt-bindings: rtc: pxa-rtc: convert to dtschema Javier Carrasco
2024-04-13 20:22 ` [PATCH v3 2/4] dt-bindings: rtc: convert trivial devices into dtschema Javier Carrasco
2024-04-15 0:09 ` Andrew Jeffery
2024-04-15 6:35 ` Javier Carrasco
2024-04-13 20:22 ` [PATCH v3 4/4] dt-bindings: rtc: stmp3xxx-rtc: convert to dtschema Javier Carrasco
2024-04-13 21:11 ` Krzysztof Kozlowski
2024-04-17 19:36 ` (subset) [PATCH v3 0/4] rtc: convert multiple bindings into dtschema Alexandre Belloni
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=20240413-rtc_dtschema-v3-0-eff368bcc471@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=linux-aspeed@lists.ozlabs.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