All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Golle <daniel@makrotopia.org>
To: Tom Rini <trini@konsulko.com>,
	Daniel Golle <daniel@makrotopia.org>,
	u-boot@lists.denx.de
Subject: [PATCH 0/2] rtc: pcf8563: HYM8563 support and unreliable-time reporting
Date: Sun, 19 Jul 2026 02:49:14 +0100	[thread overview]
Message-ID: <cover.1784423738.git.daniel@makrotopia.org> (raw)

The Haoyu HYM8563, found for example on the Radxa ROCK 5B, is a clone of
the NXP PCF8563 with an identical timekeeping register layout, but the
pcf8563 driver does not match its compatible used in upstream DT.

Boards fitted with it end up without DM_RTC and, as a consequence,
without usable EFI GetTime and SetTime runtime services. On top of
that, when the chip reports that the time may be unreliable after a
supply voltage drop, the driver returns a bare -1, which callers
interpret as -EPERM rather than as invalid data.

This series makes the existing driver serve the HYM8563 and lets callers
distinguish an unreliable time from a permission problem.

The driver gains the additional compatible string and returns -EINVAL
when the voltage-low flag is set, matching the rv3032 driver and the
behaviour of the Linux driver for the same chips.

Daniel Golle (2):
  rtc: pcf8563: add haoyu,hym8563 compatible
  rtc: pcf8563: return -EINVAL when the voltage-low flag is set

 drivers/rtc/pcf8563.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)


base-commit: ece349ade2973e220f524ce59e59711cc919263f
-- 
2.55.0

             reply	other threads:[~2026-07-19  1:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-19  1:49 Daniel Golle [this message]
2026-07-19  1:49 ` [PATCH 1/2] rtc: pcf8563: add haoyu,hym8563 compatible Daniel Golle
2026-07-20 15:42   ` Tom Rini
2026-07-19  1:49 ` [PATCH 2/2] rtc: pcf8563: return -EINVAL when the voltage-low flag is set Daniel Golle

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=cover.1784423738.git.daniel@makrotopia.org \
    --to=daniel@makrotopia.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.