From: David Heidelberg <david@ixit.cz>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-tama: Keep labibb on, so kernel can disable it
Date: Mon, 15 Dec 2025 20:07:09 +0100 [thread overview]
Message-ID: <e3590c98-785f-4774-bb57-04c65cf12d21@ixit.cz> (raw)
In-Reply-To: <ed0bdcae-6fa1-48a4-9618-e0ac09097f9e@oss.qualcomm.com>
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@ixit.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@oss.qualcomm.com>
>> Signed-off-by: David Heidelberg <david@ixit.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@oss.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!
David
>
> Konrad
--
David Heidelberg
next prev parent reply other threads:[~2025-12-15 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 11:31 David Heidelberg via B4 Relay
2025-12-02 12:55 ` Konrad Dybcio
2025-12-02 13:48 ` David Heidelberg
2025-12-15 19:07 ` David Heidelberg [this message]
2025-12-29 15:43 ` Konrad Dybcio
2026-01-05 16:42 ` Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3590c98-785f-4774-bb57-04c65cf12d21@ixit.cz \
--to=david@ixit.cz \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®