linux-kernel - Re: (subset) [PATCH 0/4] rtc: pm8xxx: fix uefi offset lookup

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] [day] [month] [year] [list]

Message-ID: <174970084180.547582.16657284509599541247.b4-ty@kernel.org>
Date: Wed, 11 Jun 2025 23:00:36 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>,
	Johan Hovold <johan+linaro@...nel.org>
Cc: Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Konrad Dybcio <konradybcio@...nel.org>,
	linux-arm-msm@...r.kernel.org,
	linux-rtc@...r.kernel.org,
	devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 0/4] rtc: pm8xxx: fix uefi offset lookup


On Wed, 23 Apr 2025 09:51:39 +0200, 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 a
> driver can take into account.
> 
> On platforms where the offset is stored in a Qualcomm specific UEFI
> variable the variables are also accessed in a non-standard way, which
> means that the OS cannot assume that the variable service is available
> by the time the driver probes.
> 
> [...]

Applied, thanks!

[3/4] arm64: dts: qcom: sc8280xp-x13s: describe uefi rtc offset
      commit: 869971de8221b97acb6aa4d7ff4fa67eb71adc87
[4/4] arm64: dts: qcom: x1e80100: describe uefi rtc offset
      commit: e8d3dc45f2d3b0fea089e0e6e351d1287a5a2a29

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>