lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z46ERygUaUxZEHuX@bogus>
Date: Mon, 20 Jan 2025 17:13:43 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Johan Hovold <johan@...nel.org>
Cc: Johan Hovold <johan+linaro@...nel.org>,
	Alexandre Belloni <alexandre.belloni@...tlin.com>,
	Sudeep Holla <sudeep.holla@....com>,
	Bjorn Andersson <andersson@...nel.org>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Konrad Dybcio <konradybcio@...nel.org>,
	Jonathan Marek <jonathan@...ek.ca>, linux-arm-msm@...r.kernel.org,
	linux-rtc@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/7] rtc: pm8xxx: add support for uefi offset

On Mon, Jan 20, 2025 at 04:17:36PM +0100, Johan Hovold wrote:
> On Mon, Jan 20, 2025 at 04:15:54PM +0100, Johan Hovold wrote:
> > On Mon, Jan 20, 2025 at 03:10:24PM +0000, Sudeep Holla wrote:
> > > On Mon, Jan 20, 2025 at 03:41:48PM +0100, Johan Hovold wrote:
> > > > On many Qualcomm platforms the PMIC RTC control and time registers are
> > > > read-only so that the RTC time can not be updated. Instead an offset
> > > > needs be stored in some machine-specific non-volatile memory, which the
> > > > driver can take into account.
> > > > 
> > > > Add support for storing a 32-bit offset from the GPS time epoch in a
> > > > UEFI variable so that the RTC time can be set on such platforms.
> > > >
> > > 
> > > Why can't the UEFI runtime services be used here ?
> > > In short, why is drivers/rtc/rtc-efi.c not working or no attempts are
> > > made to check if that works just fine ?
> > 
> > As I alluded to in the commit message, the Qualcomm UEFI implementation
> 
> s/commit message/cover letter/
>

Ah OK, Sorry for missing that and for you dealing with this mess 😄.
Never ending or very long list of quirks on Linux for the platform I imagine.

--
Regards,
Sudeep

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ