From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Frank Li <Frank.li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: rtc: pcf2127: add compatible string nxp,rtc-pcf2123
Date: Thu, 4 Sep 2025 14:06:26 +0200 [thread overview]
Message-ID: <20250904120626554f89c7@mail.local> (raw)
In-Reply-To: <20250904-mustard-lion-of-downpour-f07cea@kuoka>
On 04/09/2025 11:29:25+0200, Krzysztof Kozlowski wrote:
> On Wed, Sep 03, 2025 at 09:24:36PM +0200, Alexandre Belloni wrote:
> > On 03/09/2025 14:24:10-0400, Frank Li wrote:
> > > On Wed, Sep 03, 2025 at 06:58:29PM +0200, Alexandre Belloni wrote:
> > > > On 03/09/2025 12:55:36-0400, Frank Li wrote:
> > > > > Add compatible string nxp,rtc-pcf2123, which style is not consistent with
> > > > > existed compatible string because existed driver and dts use
> > > > > nxp,rtc-pcf2123.
> > > > >
> > > > > Fix below CHECK_DTBS warning:
> > > > > arch/arm/boot/dts/nxp/imx/imx6q-evi.dtb: /soc/bus@2000000/spba-bus@2000000/spi@2018000/rtc@3: failed to match any schema with compatible: ['nxp,rtc-pcf2123']
> > > > >
> > > > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > > > > ---
> > > > > Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml | 1 +
> > > > > 1 file changed, 1 insertion(+)
> > > > >
> > > > > diff --git a/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml b/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml
> > > > > index 11fcf0ca1ae07..595c20df6a411 100644
> > > > > --- a/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml
> > > > > +++ b/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml
> > > > > @@ -20,6 +20,7 @@ properties:
> > > > > - nxp,pcf2127
> > > > > - nxp,pcf2129
> > > > > - nxp,pcf2131
> > > > > + - nxp,rtc-pcf2123
> > > >
> > > > Nope, you need to fix the devicetree.
>
> Yep, 6 years is enough for all users to adjust, so I agree.
>
> > >
> > > Oh, driver drivers/rtc/rtc-pcf2123.c also use nxp,rtc-pcf2123. For such old
> > > devices, generally keep it as it.
> > >
> > > Maybe DT team members provide more professional comments for it.
> >
> > It is there for DT ABI compatibility, we don't need to advertise its
> > existence in the doc, you must fix the device tree.
>
> In-tree compatibles should be documented anyway (as "deprecated: true").
>
There is one device tree to fix, then we won't have any occurrence
in-tree anymore.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-09-04 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 16:55 [PATCH 1/1] dt-bindings: rtc: pcf2127: add compatible string nxp,rtc-pcf2123 Frank Li
2025-09-03 16:58 ` Alexandre Belloni
2025-09-03 18:24 ` Frank Li
2025-09-03 19:24 ` Alexandre Belloni
2025-09-04 9:29 ` Krzysztof Kozlowski
2025-09-04 12:06 ` Alexandre Belloni [this message]
2025-09-04 13:09 ` Krzysztof Kozlowski
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=20250904120626554f89c7@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=krzk@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;
as well as URLs for NNTP newsgroup(s).