devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
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 15:09:26 +0200	[thread overview]
Message-ID: <dbf8e04a-724c-455a-9b4e-865bf5192a8a@kernel.org> (raw)
In-Reply-To: <20250904120626554f89c7@mail.local>

On 04/09/2025 14:06, Alexandre Belloni wrote:
>>>>
>>>> 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.

The driver is, unless there is patch dropping it somewhere...

Best regards,
Krzysztof

      reply	other threads:[~2025-09-04 13:09 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
2025-09-04 13:09           ` Krzysztof Kozlowski [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=dbf8e04a-724c-455a-9b4e-865bf5192a8a@kernel.org \
    --to=krzk@kernel.org \
    --cc=Frank.li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).