linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Demi Marie Obenour <demiobenour@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Juergen Gross <jgross@suse.com>,
	linux-rtc@vger.kernel.org,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Ard Biesheuvel <ardb+git@google.com>,
	linux-efi@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, Bibo Mao <maobibo@loongson.cn>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	loongarch@lists.linux.dev, xen-devel@lists.xenproject.org,
	Feng Tang <feng.tang@linux.alibaba.com>,
	linux-riscv@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/3] efi-rtc: Remove wakeup functionality
Date: Mon, 14 Jul 2025 02:22:43 -0400	[thread overview]
Message-ID: <f538a1b9-6a7c-474f-af2a-d87c35b82fc5@gmail.com> (raw)
In-Reply-To: <CAMj1kXETDd+19i+awMx1v1sE4RXhF-r2a-mTa3rWfus5s4HMmw@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 1168 bytes --]

On 7/14/25 02:19, Ard Biesheuvel wrote:
> On Mon, 14 Jul 2025 at 16:13, Demi Marie Obenour <demiobenour@gmail.com> wrote:
>>
>> On 7/14/25 02:08, Ard Biesheuvel wrote:
>>> From: Ard Biesheuvel <ardb@kernel.org>
>>>
>>> The EFI rtc driver is used by non-x86 architectures only, and exposes
>>> the get/set wakeup time functionality provided by the underlying
>>> platform. This is usually broken on most platforms, and not widely used
>>> to begin with [if at all], so let's just remove it.
>> systemd uses the underlying functionality: a timer can wake the system up.
>> I have no idea if that is implemented in terms of this function, though.
> 
> To be clear, you are referring to wake from poweroff at some date/time
> in the future, right?

Yes.

> This change does not remove this functionality from the RTC subsystem,
> it just ceases to expose it on non-x86 EFI platforms that claim to
> support it.

Do these platforms generally expose the functionality in a different way?
If not, systemd should probably document that the functionality is
non-portable if it doesn't do that already.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-07-14  6:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14  6:08 [RFC PATCH 0/3] Remove unused EFI runtime APIs Ard Biesheuvel
2025-07-14  6:08 ` [RFC PATCH 1/3] efi-rtc: Remove wakeup functionality Ard Biesheuvel
2025-07-14  6:13   ` Demi Marie Obenour
2025-07-14  6:19     ` Ard Biesheuvel
2025-07-14  6:22       ` Demi Marie Obenour [this message]
2025-07-14  6:34         ` Ard Biesheuvel
2025-07-14  7:16   ` Feng Tang
2025-08-03  1:04   ` Alexandre Belloni
2025-08-09 23:02     ` Ard Biesheuvel
2025-09-14 21:16   ` (subset) " Alexandre Belloni
2025-07-14  6:08 ` [RFC PATCH 2/3] efi/test: Don't bother pseudo-testing unused EFI services Ard Biesheuvel
2025-07-14  6:08 ` [RFC PATCH 3/3] efi: Remove support for pointless, " Ard Biesheuvel
2025-07-17  0:49   ` Stefano Stabellini
2025-07-14  8:10 ` [RFC PATCH 0/3] Remove unused EFI runtime APIs Heinrich Schuchardt
2025-07-15  3:29   ` Ard Biesheuvel
2025-07-15 14:58     ` Sunil V L
2025-07-16  3:52       ` Ard Biesheuvel

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=f538a1b9-6a7c-474f-af2a-d87c35b82fc5@gmail.com \
    --to=demiobenour@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=ardb+git@google.com \
    --cc=ardb@kernel.org \
    --cc=feng.tang@linux.alibaba.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=jgross@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=maobibo@loongson.cn \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).