From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Ard Biesheuvel <ardb+git@google.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Feng Tang <feng.tang@linux.alibaba.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Sunil V L <sunilvl@ventanamicro.com>,
Bibo Mao <maobibo@loongson.cn>,
linux-rtc@vger.kernel.org, linux-efi@vger.kernel.org,
xen-devel@lists.xenproject.org, x86@kernel.org,
linux-riscv@lists.infradead.org, loongarch@lists.linux.dev
Subject: Re: [RFC PATCH 1/3] efi-rtc: Remove wakeup functionality
Date: Sun, 3 Aug 2025 03:04:49 +0200 [thread overview]
Message-ID: <20250803010449df1f5cfb@mail.local> (raw)
In-Reply-To: <20250714060843.4029171-6-ardb+git@google.com>
Hello,
Apart from the topic that should be "rtc: efi:...", I'm ready to apply
this patch.
On 14/07/2025 08:08:45+0200, 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.
>
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> drivers/rtc/rtc-efi.c | 76 +-------------------
> 1 file changed, 2 insertions(+), 74 deletions(-)
>
> diff --git a/drivers/rtc/rtc-efi.c b/drivers/rtc/rtc-efi.c
> index fa8bf82df948..b4f44999ef0f 100644
> --- a/drivers/rtc/rtc-efi.c
> +++ b/drivers/rtc/rtc-efi.c
> @@ -112,48 +112,6 @@ convert_from_efi_time(efi_time_t *eft, struct rtc_time *wtime)
> return true;
> }
>
> -static int efi_read_alarm(struct device *dev, struct rtc_wkalrm *wkalrm)
> -{
> - efi_time_t eft;
> - efi_status_t status;
> -
> - /*
> - * As of EFI v1.10, this call always returns an unsupported status
> - */
> - status = efi.get_wakeup_time((efi_bool_t *)&wkalrm->enabled,
> - (efi_bool_t *)&wkalrm->pending, &eft);
> -
> - if (status != EFI_SUCCESS)
> - return -EINVAL;
> -
> - if (!convert_from_efi_time(&eft, &wkalrm->time))
> - return -EIO;
> -
> - return rtc_valid_tm(&wkalrm->time);
> -}
> -
> -static int efi_set_alarm(struct device *dev, struct rtc_wkalrm *wkalrm)
> -{
> - efi_time_t eft;
> - efi_status_t status;
> -
> - convert_to_efi_time(&wkalrm->time, &eft);
> -
> - /*
> - * XXX Fixme:
> - * As of EFI 0.92 with the firmware I have on my
> - * machine this call does not seem to work quite
> - * right
> - *
> - * As of v1.10, this call always returns an unsupported status
> - */
> - status = efi.set_wakeup_time((efi_bool_t)wkalrm->enabled, &eft);
> -
> - dev_warn(dev, "write status is %d\n", (int)status);
> -
> - return status == EFI_SUCCESS ? 0 : -EINVAL;
> -}
> -
> static int efi_read_time(struct device *dev, struct rtc_time *tm)
> {
> efi_status_t status;
> @@ -188,17 +146,13 @@ static int efi_set_time(struct device *dev, struct rtc_time *tm)
>
> static int efi_procfs(struct device *dev, struct seq_file *seq)
> {
> - efi_time_t eft, alm;
> + efi_time_t eft;
> efi_time_cap_t cap;
> - efi_bool_t enabled, pending;
> - struct rtc_device *rtc = dev_get_drvdata(dev);
>
> memset(&eft, 0, sizeof(eft));
> - memset(&alm, 0, sizeof(alm));
> memset(&cap, 0, sizeof(cap));
>
> efi.get_time(&eft, &cap);
> - efi.get_wakeup_time(&enabled, &pending, &alm);
>
> seq_printf(seq,
> "Time\t\t: %u:%u:%u.%09u\n"
> @@ -214,26 +168,6 @@ static int efi_procfs(struct device *dev, struct seq_file *seq)
> /* XXX fixme: convert to string? */
> seq_printf(seq, "Timezone\t: %u\n", eft.timezone);
>
> - if (test_bit(RTC_FEATURE_ALARM, rtc->features)) {
> - seq_printf(seq,
> - "Alarm Time\t: %u:%u:%u.%09u\n"
> - "Alarm Date\t: %u-%u-%u\n"
> - "Alarm Daylight\t: %u\n"
> - "Enabled\t\t: %s\n"
> - "Pending\t\t: %s\n",
> - alm.hour, alm.minute, alm.second, alm.nanosecond,
> - alm.year, alm.month, alm.day,
> - alm.daylight,
> - enabled == 1 ? "yes" : "no",
> - pending == 1 ? "yes" : "no");
> -
> - if (alm.timezone == EFI_UNSPECIFIED_TIMEZONE)
> - seq_puts(seq, "Timezone\t: unspecified\n");
> - else
> - /* XXX fixme: convert to string? */
> - seq_printf(seq, "Timezone\t: %u\n", alm.timezone);
> - }
> -
> /*
> * now prints the capabilities
> */
> @@ -249,8 +183,6 @@ static int efi_procfs(struct device *dev, struct seq_file *seq)
> static const struct rtc_class_ops efi_rtc_ops = {
> .read_time = efi_read_time,
> .set_time = efi_set_time,
> - .read_alarm = efi_read_alarm,
> - .set_alarm = efi_set_alarm,
> .proc = efi_procfs,
> };
>
> @@ -271,11 +203,7 @@ static int __init efi_rtc_probe(struct platform_device *dev)
> platform_set_drvdata(dev, rtc);
>
> rtc->ops = &efi_rtc_ops;
> - clear_bit(RTC_FEATURE_UPDATE_INTERRUPT, rtc->features);
> - if (efi_rt_services_supported(EFI_RT_SUPPORTED_WAKEUP_SERVICES))
> - set_bit(RTC_FEATURE_ALARM_WAKEUP_ONLY, rtc->features);
> - else
> - clear_bit(RTC_FEATURE_ALARM, rtc->features);
> + clear_bit(RTC_FEATURE_ALARM, rtc->features);
>
> device_init_wakeup(&dev->dev, true);
>
> --
> 2.50.0.727.gbf7dc18ff4-goog
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-08-03 1:04 UTC|newest]
Thread overview: 16+ 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
2025-07-14 6:34 ` Ard Biesheuvel
2025-07-14 7:16 ` Feng Tang
2025-08-03 1:04 ` Alexandre Belloni [this message]
2025-08-09 23:02 ` Ard Biesheuvel
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=20250803010449df1f5cfb@mail.local \
--to=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=sunilvl@ventanamicro.com \
--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).