linux-kernel - Re: [PATCH] arm64: dts: qcom: sdm845-tama: Keep labibb on, so kernel can disable it

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: <29cdca5c-100a-41e0-a698-fef8935eb33c@ixit.cz>
Date: Tue, 2 Dec 2025 14:48:03 +0100
From: David Heidelberg <david@...t.cz>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 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>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-tama: Keep labibb on, so kernel
 can disable it

On 02/12/2025 13:55, Konrad Dybcio wrote:
[...]
> 
> Perhaps "keeping it on" is a little bit unfortunate in that the wording
> collides with keeping the regulator's output enabled, but anyway

Yeah, I still can't figure better wording... :(

Anyway, I'm still thinking about the driver. We disable &lab and &ibb 
node, but the parent &labibb node should be loaded. Thus - in the theory 
- driver, should operate.

I don't think it's extra important, but it sounds this should be the 
right way.

David


> 
> Reviewed-by: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
> 
> Konrad

-- 
David Heidelberg