From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Baruch Siach <baruch@tkos.co.il>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: [PATCH 0/4] dt-bindings: rtc: convert multiple devices to dtschema
Date: Sat, 23 Mar 2024 23:46:12 +0100 [thread overview]
Message-ID: <20240323-rtc-yaml-v1-0-0c5d12b1b89d@gmail.com> (raw)
This series converts the following existing bindings to dtschema:
- armada-380-rtc
- alphascale,asm9260
- digicolor-rtc (renamed to cnxt,cx92755-rtc to match compatible)
- nxp,lpc1788-rtc
All bindings include at least one compatible that is referenced in the
existing dts (arch/arm). Those dts could be tested against the new
bindings.
It might be worth mentioning that the reference to nxp,lpc1788-rtc in
arch/arm/boot/dts/nxp/lpc/lpc18xx.dtsi also includes another compatible
called nxp,lpc1850-rtc, which is not documented or supported by existing
drivers. That generates a warning when testing against nxp,lpc1788-rtc.
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
Javier Carrasco (4):
dt-bindings: rtc: armada-380-rtc: convert to dtschema
dt-bindings: rtc: alphascale,asm9260: convert to dtschema
dt-bindings: rtc: digicolor-rtc: convert to dtschema
dt-bindings: rtc: nxp,lpc1788-rtc: convert to dtschema
.../bindings/rtc/alphascale,asm9260-rtc.txt | 19 --------
.../bindings/rtc/alphascale,asm9260-rtc.yaml | 49 +++++++++++++++++++
.../devicetree/bindings/rtc/armada-380-rtc.txt | 24 ---------
.../devicetree/bindings/rtc/cnxt,cx92755-rtc.yaml | 37 ++++++++++++++
.../devicetree/bindings/rtc/digicolor-rtc.txt | 17 -------
.../bindings/rtc/marvell,armada-380-rtc.yaml | 48 ++++++++++++++++++
.../devicetree/bindings/rtc/nxp,lpc1788-rtc.txt | 21 --------
.../devicetree/bindings/rtc/nxp,lpc1788-rtc.yaml | 57 ++++++++++++++++++++++
8 files changed, 191 insertions(+), 81 deletions(-)
---
base-commit: 70293240c5ce675a67bfc48f419b093023b862b3
change-id: 20240322-rtc-yaml-473335cbf911
Best regards,
--
Javier Carrasco <javier.carrasco.cruz@gmail.com>
next reply other threads:[~2024-03-23 22:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 22:46 Javier Carrasco [this message]
2024-03-23 22:46 ` [PATCH 1/4] dt-bindings: rtc: armada-380-rtc: convert to dtschema Javier Carrasco
2024-03-23 23:37 ` Alexandre Belloni
2024-03-24 0:02 ` Javier Carrasco
2024-03-25 16:02 ` Rob Herring
2024-03-23 22:46 ` [PATCH 2/4] dt-bindings: rtc: alphascale,asm9260: " Javier Carrasco
2024-03-23 22:46 ` [PATCH 3/4] dt-bindings: rtc: digicolor-rtc: " Javier Carrasco
2024-03-25 16:01 ` Rob Herring
2024-03-25 19:46 ` Javier Carrasco
2024-03-25 20:03 ` Krzysztof Kozlowski
2024-03-23 22:46 ` [PATCH 4/4] dt-bindings: rtc: nxp,lpc1788-rtc: " Javier Carrasco
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=20240323-rtc-yaml-v1-0-0c5d12b1b89d@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=baruch@tkos.co.il \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).