From: sashiko-bot@kernel.org
To: "Igor Velkov" <iav@iav.lv>
Cc: linux-rtc@vger.kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH RFC 3/3] arm64: dts: amlogic: meson-sm1-odroid-hc4: Describe which RTC wakes the board
Date: Wed, 04 Nov 2026 06:01:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-196713@kernel.org> (raw)
In-Reply-To: <20261104-b4-alarmtimer-rtc-priority-v1-3-e996681b8086@iav.lv>
> From: Igor Velkov <iav@iav.lv>
>
> The board has two RTCs with an alarm. The pcf8563 interrupt line goes
> to GPIOX_5, so once that interrupt is described [1], its alarm wakes the
> board from s2idle but not from deep sleep. meson-vrtc is a register the
> SoC firmware reads when the application processors suspend, so it wakes
> the board from deep sleep only, and only with a BL301 that handles its
> alarm.
>
> List the states per RTC, so that alarmtimer programs the pcf8563 for
> s2idle and meson-vrtc for deep sleep.
>
> Link: https://lore.kernel.org/r/20261020-hc4-rtc-alarm-irq-v1-1-b2b8c68d54f5@iav.lv [1]
> Signed-off-by: Igor Velkov <iav@iav.lv>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261104-b4-alarmtimer-rtc-priority-v1-0-e996681b8086@iav.lv?part=3
next prev parent reply other threads:[~2026-11-04 6:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 5:54 [PATCH RFC 0/3] alarmtimer: Choose the wakeup RTC per sleep state from the device tree Igor Velkov via B4 Relay
2026-11-04 5:54 ` Igor Velkov
2026-11-04 5:54 ` Igor Velkov via B4 Relay
2026-11-04 5:54 ` [PATCH RFC 1/3] dt-bindings: rtc: Add linux,wakeup-states and linux,alarmtimer-priority Igor Velkov via B4 Relay
2026-11-04 5:54 ` Igor Velkov
2026-11-04 5:54 ` Igor Velkov via B4 Relay
2026-11-04 6:06 ` sashiko-bot
2026-11-04 6:06 ` sashiko-bot
2026-11-04 5:54 ` [PATCH RFC 2/3] alarmtimer: Choose the wakeup RTC by sleep state and priority Igor Velkov via B4 Relay
2026-11-04 5:54 ` Igor Velkov
2026-11-04 5:54 ` Igor Velkov via B4 Relay
2026-11-04 6:03 ` sashiko-bot
2026-11-04 5:54 ` [PATCH RFC 3/3] arm64: dts: amlogic: meson-sm1-odroid-hc4: Describe which RTC wakes the board Igor Velkov via B4 Relay
2026-11-04 5:54 ` Igor Velkov
2026-11-04 5:54 ` Igor Velkov via B4 Relay
2026-11-04 6:01 ` sashiko-bot [this message]
2026-11-04 8:50 ` [PATCH RFC 0/3] alarmtimer: Choose the wakeup RTC per sleep state from the device tree Neil Armstrong
2026-11-04 8:50 ` Neil Armstrong
2026-11-04 18:38 ` Igor Velkov
2026-11-04 18:38 ` Igor Velkov
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-196713@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=iav@iav.lv \
--cc=linux-rtc@vger.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 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.