linux-kernel - Re: [PATCH 17/24] arm64: dts: qcom: glymur-crd: Avoid RTC probe failure

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: <CAJKOXPdi0+c_FqinVA0gzoyqG6FVFp0jq5WSLsWWKiT12VVs3Q@mail.gmail.com>
Date: Thu, 25 Sep 2025 17:11:25 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Pankaj Patil <pankaj.patil@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Kamal Wadhwa <kamal.wadhwa@....qualcomm.com>
Subject: Re: [PATCH 17/24] arm64: dts: qcom: glymur-crd: Avoid RTC probe failure

On Thu, 25 Sept 2025 at 15:34, Pankaj Patil
<pankaj.patil@....qualcomm.com> wrote:
>
> From: Kamal Wadhwa <kamal.wadhwa@....qualcomm.com>
>
> On Glymur boards, the RTC alarm interrupts are routed to SOCCP
> subsystems and are not available to APPS. This can cause the
> RTC probe failure as the RTC IRQ registration will fail in
> probe.
>
> Fix this issue by adding `no-alarm` property in the RTC DT
> node. This will skip the RTC alarm irq registration and
> the RTC probe will return success.


This is ridiculous. You just added glymur CRD and you claim now that
it's broken and you need to fix it. So just fix that commit!

This is gross misinterpretation of splitting patchset, some twisted
LWN stats work.

NAK