From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rodrigo Rea <rodrigo.rea@marsrover.mx>
Cc: alexandre.belloni@bootlin.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
alexander.stein@ew.tq-group.com, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
rodrigo.rea@nxp.com, daniel.aguirre@nxp.com
Subject: Re: [PATCH v2] dt-bindings: rtc: pcf85063: Add NXP PCA85074A
Date: Tue, 10 Nov 2026 12:55:19 +0100 [thread overview]
Message-ID: <20261110-provocative-voracious-parakeet-dfc33a@quoll> (raw)
In-Reply-To: <20261109152352.6335-1-rodrigo.rea@marsrover.mx>
On Mon, Nov 09, 2026 at 03:24:02PM +0000, Rodrigo Rea wrote:
> From: Rodrigo Rea <rodrigo.rea@nxp.com>
>
> Document the NXP PCA85074A real-time clock with nxp,pca85073a as a
> fallback compatible. Both devices have the same register layout for
> clock, calendar, alarm, offset, RAM and timer functions, allowing the
> existing PCA85073A driver support to be used without a new match entry.
>
> Link: https://www.nxp.com/docs/en/data-sheet/PCA85074A.pdf
> Signed-off-by: Rodrigo Rea <rodrigo.rea@nxp.com>
> ---
> Changes in v2:
> - Require nxp,pca85073a as the fallback compatible, as requested by
> Conor Dooley.
> - Drop the driver patch: the existing fallback match provides DT support.
> - No runtime test of the new fallback DT has been performed.
>
> Link to v1:
> https://lore.kernel.org/20261105215204.2446733-1-rodrigo.rea@marsrover.mx/
>
> .../devicetree/bindings/rtc/nxp,pcf85063.yaml | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-10 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 15:24 Rodrigo Rea
2026-11-10 11:55 ` 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=20261110-provocative-voracious-parakeet-dfc33a@quoll \
--to=krzk@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=daniel.aguirre@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rodrigo.rea@marsrover.mx \
--cc=rodrigo.rea@nxp.com \
/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
all inboxes | Powered by JetHome®