From: "Rafael J. Wysocki" <rafael@kernel.org>
To: linux-rtc@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v1 0/2] rtc: cmos: Do not require IRQ if ACPI alarm is used
Date: Sat, 14 Mar 2026 13:09:21 +0100 [thread overview]
Message-ID: <3964452.kQq0lBPeGt@rafael.j.wysocki> (raw)
Hi All,
This series of patches allows the CMOS RTC alarm to be used on x86
systems that don't include a functional HPET and may not configure
an IRQ for the CMOS RTC, but have a functional ACPI RTC fixed event.
The first patch allows the ACPI RTC fixed event to be used on systems
without functional HPET because there is no fundamental dependency
between HPET and the ACPI RTC fixed event being hooked up to the CMOS
RTC.
The second patch changes the driver to stop requiring an IRQ to be
configured for the alarm functionality if the ACPI RTC fixed event
is use for signaling events because it require a separate IRQ to
be requested (the ACPI SCI is used for event signaling in that case).
Thanks!
next reply other threads:[~2026-03-14 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 12:09 Rafael J. Wysocki [this message]
2026-03-14 12:11 ` [PATCH v1 1/2] rtc: cmos: Enable ACPI alarm if advertised in ACPI FADT Rafael J. Wysocki
2026-03-20 18:00 ` Alexandre Belloni
2026-03-20 19:26 ` Mario Limonciello (AMD) (kernel.org)
2026-03-14 12:12 ` [PATCH v1 2/2] rtc: cmos: Do not require IRQ if ACPI alarm is used Rafael J. Wysocki
2026-03-20 18:00 ` Alexandre Belloni
2026-03-20 19:27 ` Mario Limonciello (AMD) (kernel.org)
2026-03-20 15:56 ` [PATCH v1 0/2] " Rafael J. Wysocki
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=3964452.kQq0lBPeGt@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mario.limonciello@amd.com \
/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
all inboxes | Powered by JetHome®