From: Conor Dooley <conor@kernel.org>
To: "Baek Kyu, Kim" <pocj8ur4in@gmail.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
linux-rtc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: mpfs: Fix alarm register word order
Date: Tue, 20 Oct 2026 11:17:43 +0100 [thread overview]
Message-ID: <20261020-frequency-gloating-f9fd455d4fd2@spud> (raw)
In-Reply-To: <20261019151024.2232338-1-pocj8ur4in@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]
On Tue, Oct 20, 2026 at 12:10:24AM +0900, Baek Kyu, Kim wrote:
> mpfs_rtc_readalarm() swaps the low and high words of the alarm time.
> The RTC core reads this value during device registration to initialize
> its alarm timer. This can populate the cached alarm and timer queue
> with an incorrect expiry time, or leave an enabled hardware alarm out
> of the timer queue if the decoded time appears to be in the past.
>
> Read the low 32 bits from ALARM_LOWER_REG and place the masked high
> 11 bits from ALARM_UPPER_REG in bits 42:32. This matches the layout
> used by mpfs_rtc_setalarm() and the low/high assembly in
> mpfs_rtc_readtime(), so the RTC core imports the programmed alarm
> time correctly during device registration.
>
> Fixes: 0b31d703598d ("rtc: Add driver for Microchip PolarFire SoC")
> Signed-off-by: Baek Kyu, Kim <pocj8ur4in@gmail.com>
That's very odd, wonder how that happened. Definitely a blindspot when
it came to testing. This should look the same as reading the time.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
CC: stable@vger.kernel.org
Cheers,
Conor.
> ---
> Tested with KUnit under ARM64 QEMU using RAM-backed MMIO and the actual
> MPFS RTC callbacks and RTC core registration. All ten tests pass with the
> fix, including importing a preloaded alarm and checking its timer queue
> entry. Four additional tests covering current-date alarms also pass.
> No physical MPFS hardware or suspend/wakeup was tested.
>
> drivers/rtc/rtc-mpfs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/rtc/rtc-mpfs.c b/drivers/rtc/rtc-mpfs.c
> index 60596b0ea9d8..6616ca1f02c7 100644
> --- a/drivers/rtc/rtc-mpfs.c
> +++ b/drivers/rtc/rtc-mpfs.c
> @@ -131,8 +131,8 @@ static int mpfs_rtc_readalarm(struct device *dev, struct rtc_wkalrm *alrm)
>
> alrm->enabled = mode & MODE_WAKE_EN;
>
> - time = (u64)readl(rtcdev->base + ALARM_LOWER_REG) << 32;
> - time |= (readl(rtcdev->base + ALARM_UPPER_REG) & ALARM_UPPER_MASK);
> + time = readl(rtcdev->base + ALARM_LOWER_REG);
> + time |= ((u64)readl(rtcdev->base + ALARM_UPPER_REG) & ALARM_UPPER_MASK) << 32;
> rtc_time64_to_tm(time, &alrm->time);
>
> return 0;
>
> base-commit: 58161ead29e50d70a317ea26b472e0c7508e69da
> --
> 2.55.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-20 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 15:10 [PATCH] rtc: mpfs: Fix alarm register word order Baek Kyu, Kim
2026-10-19 16:10 ` sashiko-bot
2026-10-20 10:17 ` Conor Dooley [this message]
2026-10-20 12:41 ` Alexandre Belloni
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=20261020-frequency-gloating-f9fd455d4fd2@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=pocj8ur4in@gmail.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