[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c43b59bb-b073-497e-a9c6-c9c98e6a1fdf@amd.com>
Date: Fri, 17 Nov 2023 17:00:56 -0600
From: Mario Limonciello <mario.limonciello@....com>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: Pavel Machek <pavel@....cz>,
Alessandro Zummo <a.zummo@...ertech.it>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
alvin.zhuge@...il.com, renzhamin@...il.com, kelvie@...vie.ca,
Raul Rangel <rrangel@...gle.com>
Subject: Re: [PATCH] rtc: cmos: Use ACPI alarm for non-Intel x86 systems too
On 11/17/2023 16:57, Alexandre Belloni wrote:
> On 14/11/2023 18:15:02-0600, Mario Limonciello wrote:
>> On 11/14/2023 16:28, Alexandre Belloni wrote:
>>> On 14/11/2023 10:06:36+0100, Pavel Machek wrote:
>>>> On Mon 2023-11-13 23:38:19, Alexandre Belloni wrote:
>>>>> On 13/11/2023 15:36:28-0600, Mario Limonciello wrote:
>>>>>> Now that the merge window is over, can this be picked up?
>>>>>>
>>>>>
>>>>> I'd be happy to invoice AMD so they get a quick response time.
>>>>
>>>> That is a really bad joke.
>>>
>>> Why would it be a joke?
>>>
>>> From what I get this is an issue since 2021, I don't get how this is so
>>> urgent that I get a ping less than 24h after the end of the merge
>>> window.
>>
>> It's possibly longer; but I don't have a large enough sample to say that
>> it's safe that far back.
>
> Would this help this one:
> https://bugzilla.kernel.org/show_bug.cgi?id=68331
>
The BIOS cutoff is set to 2021 in my patch, so unless they have an
updated BIOS for that system I think it's unlikely to do anything.
They can certainly try with the kernel command line though to see if it
could help. If it does we could add another case for it or adjust
boundaries.
Powered by blists - more mailing lists