From: Shanker Donthineni <sdonthineni@nvidia.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ard Biesheuvel <ardb@kernel.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-efi@vger.kernel.org
Subject: Re: [PATCH 1/1] efi: rtc: Enable SET/GET WAKEUP services as optional
Date: Mon, 2 Jan 2023 16:57:02 -0600 [thread overview]
Message-ID: <a7f6e0ae-3fbc-ccf7-6185-a425ad25e04f@nvidia.com> (raw)
In-Reply-To: <Y7NY+ba2USk7hEAx@mail.local>
Hi Alexandre Belloni,
On 1/2/23 16:21, Alexandre Belloni wrote:
> On 02/01/2023 11:47:11+0100, Ard Biesheuvel wrote:
>> On Tue, 27 Dec 2022 at 05:09, Shanker Donthineni<sdonthineni@nvidia.com> wrote:
>>> The current implementation of rtc-efi is expecting all the 4
>>> time services GET{SET}_TIME{WAKEUP} must be supported by UEFI
>>> firmware. As per the EFI_RT_PROPERTIES_TABLE, the platform
>>> specific implementations can choose to enable selective time
>>> services based on the RTC device capabilities.
>>>
>>> This patch does the following changes to provide GET/SET RTC
>>> services on platforms that do not support the WAKEUP feature.
>>>
>>> 1) Relax time services cap check when creating a platform device.
>>> 2) Clear RTC_FEATURE_ALARM bit in the absence of WAKEUP services.
>>> 3) Conditional alarm entries in '/proc/driver/rtc'.
>>>
>>> Signed-off-by: Shanker Donthineni<sdonthineni@nvidia.com>
>> Queued as a fix in efi/urgent, thanks.
> This rather seems like an rtc heavy patch and the subject line is
> misleading. This should be rtc: efi:
> Also, I'm pretty sure this doesn't qualify as an urgent fix.
>
Thanks, I'll post v2 patch with your suggested subject.
next prev parent reply other threads:[~2023-01-02 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 4:09 [PATCH 1/1] efi: rtc: Enable SET/GET WAKEUP services as optional Shanker Donthineni
2023-01-02 10:47 ` Ard Biesheuvel
2023-01-02 22:21 ` Alexandre Belloni
2023-01-02 22:57 ` Shanker Donthineni [this message]
2023-01-03 9:18 ` Ard Biesheuvel
2023-01-03 16:36 ` Shanker Donthineni
2023-01-03 16:37 ` 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=a7f6e0ae-3fbc-ccf7-6185-a425ad25e04f@nvidia.com \
--to=sdonthineni@nvidia.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=ardb@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox