Linux RTC
 help / color / mirror / Atom feed
From: Udaya Kiran Challa <challauday369@gmail.com>
To: alexandre.belloni@bootlin.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: skhan@linuxfoundation.org, me@brighamcampbell.com,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Udaya Kiran Challa <challauday369@gmail.com>
Subject: [PATCH v2] dt-bindings: rtc: epson,rx6110: Convert to DT Schema
Date: Sat,  9 May 2026 14:30:51 +0530	[thread overview]
Message-ID: <20260509090051.77603-1-challauday369@gmail.com> (raw)

Convert the Epson RX6110 Real Time Clock devicetree binding
from the legacy text format to DT schema.

Signed-off-by: Udaya Kiran Challa <challauday369@gmail.com>
---
Changelog:
Changes since v1:
- Reuse common SPI peripheral properties
- Drop redundant SPI-specific comment
- Remove unused labels from examples

Link to v1:https://lore.kernel.org/all/20260504183728.27412-1-challauday369@gmail.com/
---
 .../devicetree/bindings/rtc/epson,rx6110.yaml | 23 +++++++------------
 1 file changed, 8 insertions(+), 15 deletions(-)

diff --git a/Documentation/devicetree/bindings/rtc/epson,rx6110.yaml b/Documentation/devicetree/bindings/rtc/epson,rx6110.yaml
index 32d15a014f91..b51d39ef75e4 100644
--- a/Documentation/devicetree/bindings/rtc/epson,rx6110.yaml
+++ b/Documentation/devicetree/bindings/rtc/epson,rx6110.yaml
@@ -14,6 +14,9 @@ description: |
 maintainers:
   - Alexandre Belloni <alexandre.belloni@bootlin.com>
 
+allOf:
+  - $ref: /schemas/spi/spi-peripheral-props.yaml#
+
 properties:
   compatible:
     const: epson,rx6110
@@ -21,24 +24,14 @@ properties:
   reg:
     maxItems: 1
 
-  # SPI-specific properties
-  spi-cs-high:
-    type: boolean
-    description: RX6110 needs chipselect high
-
-  spi-cpha:
-    type: boolean
-    description: RX6110 works with SPI shifted clock phase
-
-  spi-cpol:
-    type: boolean
-    description: RX6110 works with SPI inverse clock polarity
+  spi-cpha: true
+  spi-cpol: true
 
 required:
   - compatible
   - reg
 
-additionalProperties: false
+unevaluatedProperties: false
 
 examples:
   # I2C mode
@@ -47,7 +40,7 @@ examples:
       #address-cells = <1>;
       #size-cells = <0>;
 
-      rtc1: rtc@32 {
+      rtc@32 {
         compatible = "epson,rx6110";
         reg = <0x32>;
       };
@@ -59,7 +52,7 @@ examples:
       #address-cells = <1>;
       #size-cells = <0>;
 
-      rtc2: rtc@3 {
+      rtc@3 {
         compatible = "epson,rx6110";
         reg = <3>;
         spi-cs-high;
-- 
2.43.0


             reply	other threads:[~2026-05-09  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09  9:00 Udaya Kiran Challa [this message]
2026-05-09 15:58 ` [PATCH v2] dt-bindings: rtc: epson,rx6110: Convert to DT Schema Conor Dooley
  -- strict thread matches above, loose matches on Subject: below --
2026-05-09  9:47 Udaya Kiran Challa

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=20260509090051.77603-1-challauday369@gmail.com \
    --to=challauday369@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.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