All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johnny Fan <johnny.fan@cixtech.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-rtc@vger.kernel.org,
	Feng Tang <feng.tang@linux.alibaba.com>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	cix-kernel-upstream <cix-kernel-upstream@cixtech.com>,
	Bob Zhang <bob.zhang@cixtech.com>, Jie Fu <jie.fu@cixtech.com>
Subject: Re: [PATCH] rtc: efi: restore alarm support with runtime capability probe
Date: Fri, 28 Aug 2026 16:23:05 +0800	[thread overview]
Message-ID: <apFFaaJr4xlcp4mo@JohnnyFan> (raw)
In-Reply-To: <549999fa-4b1a-4f53-872a-9036a377f8cf@app.fastmail.com>

On Fri, Aug 28, 2026 at 09:26:42AM +0200, Ard Biesheuvel wrote:
> Why does it need working alarm/wakeup support?
> 
> I'm not saying we shouldn't bring it back, but this deserves a bit of
> motivation, no?

Hi Ard,

Thanks for the review.

The reason is wakeup: on CIX platforms, the RTC is an I2C device
owned by firmware, and in the ACPI boot configuration the bus is
not exposed to the OS, so the EFI runtime services are the only
way Linux can program the RTC alarm at all. With it removed,
'rtcwake' fails for both suspend-to-RAM and power-off wakeup --
Linux simply has no other path to set an alarm on this platform.

It is also a cross-OS consistency thing: Windows programs the
same alarm through the same runtime services, so a shared
interface that is time-only on the Linux side is asymmetric.

I'll extend the commit message with this motivation in v2.

Thanks,
Johnny 

  reply	other threads:[~2026-08-28  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  3:15 [PATCH] rtc: efi: restore alarm support with runtime capability probe Johnny.Fan
2026-08-28  3:32 ` sashiko-bot
2026-08-28  7:26 ` Ard Biesheuvel
2026-08-28  8:23   ` Johnny Fan [this message]
2026-08-28  8:32   ` Johnny Fan
2026-08-28 10:13     ` Ard Biesheuvel
2026-08-28 12:48       ` 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=apFFaaJr4xlcp4mo@JohnnyFan \
    --to=johnny.fan@cixtech.com \
    --cc=ardb@kernel.org \
    --cc=bob.zhang@cixtech.com \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=feng.tang@linux.alibaba.com \
    --cc=jie.fu@cixtech.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    /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.