Linux RTC
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sasha Levin" <sashal@kernel.org>
Cc: linux-rtc@vger.kernel.org,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH AUTOSEL 6.18-5.10] rtc: ds1307: fix RX8130 wakeup alarm WADA bit for day-of-month mode
Date: Mon, 19 Oct 2026 14:04:54 +0000	[thread overview]
Message-ID: <sashiko-outbox-177277@kernel.org> (raw)
In-Reply-To: <20261019135441.1420968-36-sashal@kernel.org>

> From: Robert Leussler <robert.leussler@leica-geosystems.com>
> 
> [ Upstream commit 878d93aaa596a861dbc8d71f7c38e62a2e805f01 ]
> 
> The RX8130 wakeup alarm never fired when set via
> /sys/class/rtc/rtc0/wakealarm. The root cause is that the WADA bit
> (bit 3) in the Extension register (0x1c) was never set before
> programming the alarm registers.
> 
> Per the RX8130 datasheet:
> WADA=0 - Week alarm: register 0x19 is compared against day-of-week
> WADA=1 - Day alarm:  register 0x19 is compared against day-of-month
> 
> rx8130_set_alarm() always writes a BCD day-of-month value to alarm
> register 0x19, so WADA must be 1. With WADA=0 the hardware matched the
> day-of-month value (e.g. 15) as a day-of-week index, which is always
> out of range (valid weekdays are 0-6), so the alarm interrupt was never
> asserted.
> 
> Fix by setting the WADA bit in rx8130_set_alarm() before writing the
> Extension register back to the device.
> 
> This is consistent with rx8130_read_alarm(), which decodes the same
> register under the same assumption (24-hour and day-of-month mode).
> 
> Signed-off-by: Robert Leussler <robert.leussler@leica-geosystems.com>
> Link: https://patch.msgid.link/20260721081907.3518648-1-robert.leussler@leica-geosystems.com
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> Signed-off-by: Sasha Levin <sashal@kernel.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261019135441.1420968-36-sashal@kernel.org?part=1


  reply	other threads:[~2026-10-19 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261019135441.1420968-1-sashal@kernel.org>
2026-10-19 13:45 ` [PATCH AUTOSEL 6.18-5.10] rtc: ds1307: fix RX8130 wakeup alarm WADA bit for day-of-month mode Sasha Levin
2026-10-19 14:04   ` sashiko-bot [this message]
2026-10-19 13:51 ` [PATCH AUTOSEL 6.18-5.10] rtc: brcmstb-waketimer: add missing MODULE_DEVICE_TABLE() Sasha Levin
2026-10-19 15:02   ` sashiko-bot
2026-10-19 13:51 ` [PATCH AUTOSEL 6.18-5.10] rtc: ab-eoz9: " Sasha Levin
2026-10-19 15:04   ` sashiko-bot

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=sashiko-outbox-177277@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-rtc@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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