From: Conor Dooley <conor@kernel.org>
To: Anushka Badhe <anushkabadhe@gmail.com>
Cc: alexandre.belloni@bootlin.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, dsd@laptop.org, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH v2] dt-bindings: rtc: add olpc,xo1-rtc to trivial-rtc
Date: Wed, 25 Mar 2026 17:49:39 +0000 [thread overview]
Message-ID: <20260325-aflutter-waged-2c3af1f1bb4b@spud> (raw)
In-Reply-To: <20260325093003.44051-1-anushkabadhe@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]
On Wed, Mar 25, 2026 at 03:00:03PM +0530, Anushka Badhe wrote:
> Add the OLPC XO-1 RTC compatible string to the trivial-rtc schema
> instead of creating a standalone binding file, as it only requires
> a compatible property with no additional configuration.
>
> Signed-off-by: Anushka Badhe <anushkabadhe@gmail.com>
> ---
>
> Changes in v2:
> - Move binding to trivial-rtc.yaml instead of separate file
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Please don't send new versions in response to old ones.
pw-bot: not-applicable
Cheers,
Conor.
>
> Note:
> * This patch is part of the GSoC2026 application process for device tree
> bindings conversions
> * https://github.com/LinuxFoundationGSoC/ProjectIdeas/wiki/GSoC-2026-Device-Tree-Bindings
>
> Documentation/devicetree/bindings/rtc/olpc-xo1-rtc.txt | 5 -----
> Documentation/devicetree/bindings/rtc/trivial-rtc.yaml | 2 ++
> 2 files changed, 2 insertions(+), 5 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/rtc/olpc-xo1-rtc.txt
>
> diff --git a/Documentation/devicetree/bindings/rtc/olpc-xo1-rtc.txt b/Documentation/devicetree/bindings/rtc/olpc-xo1-rtc.txt
> deleted file mode 100644
> index a2891ceb6344..000000000000
> --- a/Documentation/devicetree/bindings/rtc/olpc-xo1-rtc.txt
> +++ /dev/null
> @@ -1,5 +0,0 @@
> -OLPC XO-1 RTC
> -~~~~~~~~~~~~~
> -
> -Required properties:
> - - compatible : "olpc,xo1-rtc"
> diff --git a/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml b/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> index b47822370d6f..722176c831aa 100644
> --- a/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> +++ b/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> @@ -65,6 +65,8 @@ properties:
> - microcrystal,rv3029
> # Real Time Clock
> - microcrystal,rv8523
> + # OLPC XO-1 RTC
> + - olpc,xo1-rtc
> # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
> - ricoh,r2025sd
> # I2C bus SERIAL INTERFACE REAL-TIME CLOCK IC
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-03-25 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 8:47 [PATCH] dt-bindings: rtc: Convert olpc,xo1-rtc to DT schema Anushka Badhe
2026-03-25 8:54 ` Alexandre Belloni
2026-03-25 9:30 ` [PATCH v2] dt-bindings: rtc: add olpc,xo1-rtc to trivial-rtc Anushka Badhe
2026-03-25 17:49 ` Conor Dooley [this message]
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=20260325-aflutter-waged-2c3af1f1bb4b@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=anushkabadhe@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsd@laptop.org \
--cc=krzk+dt@kernel.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