From: Conor Dooley <conor@kernel.org>
To: Sander Speetjens <sander.speetjens@gmail.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Jonathan Bell <jonathan@raspberrypi.com>,
Stefan Wahren <wahrenst@gmx.net>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/2] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC
Date: Wed, 23 Sep 2026 17:49:18 +0100 [thread overview]
Message-ID: <20260923-basically-slider-df357b773907@spud> (raw)
In-Reply-To: <6de301bd-0bb6-4704-8c3f-8da09c5f6830@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
On Wed, Sep 23, 2026 at 06:46:00PM +0200, Sander Speetjens wrote:
> > Is this actually needed? Shouldn't the type of uint32 come from the same
> > source that the type in rtc.yaml does? Or is this missing in dt-schema?
>
> The rtc.yaml does only provide the description not the type, I also expected
> the type to be there.
>
I think this should be dropped and the type added to
property-units.yaml, I don't know where the one in rtc.yaml is getting a
type from.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-23 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 13:13 [PATCH v4 0/2] Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-23 13:13 ` [PATCH v4 1/2] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC Sander Speetjens
2026-09-23 13:21 ` sashiko-bot
2026-09-23 16:37 ` Conor Dooley
2026-09-23 16:46 ` Sander Speetjens
2026-09-23 16:49 ` Conor Dooley [this message]
2026-09-23 13:13 ` [PATCH v4 2/2] rtc: Add Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-23 13:29 ` sashiko-bot
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=20260923-basically-slider-df357b773907@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jonathan@raspberrypi.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sander.speetjens@gmail.com \
--cc=wahrenst@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.