[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <98e90787-885e-4e9f-a854-4a756e33ec9f@oss.qualcomm.com>
Date: Mon, 29 Dec 2025 16:43:16 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: David Heidelberg <david@...t.cz>, 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>,
"marijn.suijten@...ainline.org" <marijn.suijten@...ainline.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 12/15/25 8:07 PM, David Heidelberg wrote:
> On 02/12/2025 13:55, Konrad Dybcio wrote:
>> On 12/2/25 12:31 PM, David Heidelberg via B4 Relay wrote:
>>> From: David Heidelberg <david@...t.cz>
>>>
>>> In case if they were enabled by the bootloader as part of some
>>> reference/common routine and left hanging. Linux will switch them off if
>>> they're never used.
>>>
>>> Discussion about it can be found here:
>>> https://lore.kernel.org/all/20251130-oneplus-labibb-v1-1-bb3653e43120@ixit.cz/
>>>
>>> Fixes: 5dcc6587fde2 ("arm64: dts: qcom: sdm845-tama: Add display nodes")
>>> Suggested-by: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
>>> Signed-off-by: David Heidelberg <david@...t.cz>
>>> ---
>>
>> Perhaps "keeping it on" is a little bit unfortunate in that the wording
>> collides with keeping the regulator's output enabled, but anyway
>>
>> Reviewed-by: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
>
> So, friend fixed tama-akatsuki against -next tree and having labibb nodes there crashes the kernel, so it seems disabling labibb had some reason.
>
> So, please do not merge until figured out!
+Marijn could you take a look?
Konrad
Powered by blists - more mailing lists