Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: David Heidelberg <david@ixit.cz>,
	Casey Connolly <casey.connolly@linaro.org>,
	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, phone-devel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-oneplus: labibb is not used on OnePlus 6/6T
Date: Tue, 2 Dec 2025 11:40:52 +0100	[thread overview]
Message-ID: <fdb5e8df-017f-4891-b004-5ef919447962@oss.qualcomm.com> (raw)
In-Reply-To: <63ad4e46-8450-4ec4-bb13-6701f5eec5f6@ixit.cz>

On 12/1/25 10:55 PM, David Heidelberg wrote:
> On 01/12/2025 13:57, Casey Connolly wrote:
>>
>>
>> On 01/12/2025 13:55, Konrad Dybcio wrote:
>>> On 12/1/25 1:50 PM, Casey Connolly wrote:
>>>>
>>>>
>>>> On 01/12/2025 13:48, Konrad Dybcio wrote:
>>>>> On 11/30/25 1:08 AM, David Heidelberg via B4 Relay wrote:
>>>>>> From: David Heidelberg <david@ixit.cz>
>>>>>>
>>>>>> The lab and ibb regulators aren't used here. Disable them.
>>>>>>
>>>>>> Removes following warnings:
>>>>>> qcom-lab-ibb-regulator c440000.spmi:pmic@3:labibb: Failed to create device link (0x180) with supplier c440000.spmi for /soc@0/spmi@c440000/pmic@3/labibb/lab
>>>>>> qcom-lab-ibb-regulator c440000.spmi:pmic@3:labibb: Failed to create device link (0x180) with supplier c440000.spmi for /soc@0/spmi@c440000/pmic@3/labibb/ibb
>>>>>
>>>>> These are only vaguely related, as there's nothing to be wary about that's
>>>>> specific to these devices - it's just devlink being grumpy
>>>>>
>>>>>> Fixes: 288ef8a42612 ("arm64: dts: sdm845: add oneplus6/6t devices")
>>>>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>>>>> ---
>>>>>> I assume this is right approach, as OLEDs on both devices are driven by
>>>>>> different regulators.
>>>>>>
>>>>>> Question is, if should be labibb nodes enabled by default?
>>>>>
>>>>> They're onboard. I'd rather keep them predictably parked than left in
>>>>> whatever (potentially ON) state the bootloader may leave them at
>>>>
>>>> Shouldn't they be default disabled in the pmic dtsi and only enabled on
>>>> the devices that actually use them? Many SDM845 devices with OLED panels
>>>> don't use these regulators.
>>>
>>> As I said, I wouldn't be surprised 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 and I'm fairly sure the users won't
>>> mind the odd couple dozen bytes of runtime kernel memory usage (which if
>>> we go that route probably balance out with the added couple characters for
>>> status=disabled in the resulting DTB)
>>
>> Ahh yeah I understand, the DT node has to be enabled for the driver to
>> load and actually turn off the regulators if they're unused. Makes sense.
>>
>> Thanks,>
>>> Konrad
>>
> 
> Thank you both, now I also understand (and withdrawing the patch).
> 
> Should
> 
> 5dcc6587fde2 ("arm64: dts: qcom: sdm845-tama: Add display nodes")
> 
> also get fixed up to not disable the lab & ibb node then?

Yes

Konrad

      reply	other threads:[~2025-12-02 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-30  0:08 [PATCH] arm64: dts: qcom: sdm845-oneplus: labibb is not used on OnePlus 6/6T David Heidelberg via B4 Relay
2025-12-01 12:48 ` Konrad Dybcio
2025-12-01 12:50   ` Casey Connolly
2025-12-01 12:55     ` Konrad Dybcio
2025-12-01 12:57       ` Casey Connolly
2025-12-01 21:55         ` David Heidelberg
2025-12-02 10:40           ` Konrad Dybcio [this message]

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=fdb5e8df-017f-4891-b004-5ef919447962@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=casey.connolly@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@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