From: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>,
Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: bjorn.andersson@oss.qualcomm.com,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
laurentiu.tudor1@dell.com
Subject: Re: [PATCH] arm64: dts: qcom: x1e80100-dell-xps13-9345: Disable PM8010
Date: Sun, 15 Jun 2025 20:29:07 +0200 [thread overview]
Message-ID: <d2eabc30-f1d2-47d8-82f9-86f6f7a705bb@gmail.com> (raw)
In-Reply-To: <a7zyhmv5lqxl2l5rdg2x5g55wokm6ztwvzwrfkyeignwdromjr@afpe7zwsmkt2>
On 3/19/25 15:00, Bjorn Andersson wrote:
> On Wed, Mar 19, 2025 at 11:06:12AM +0100, Stephan Gerhold wrote:
>> On Tue, Mar 18, 2025 at 10:17:02PM -0500, Bjorn Andersson via B4 Relay wrote:
>>> From: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
>>>
>>> The Qualcomm X Elite reference design uses the PM8010 PMIC for camera
>>> use cases, but the Dell XPS13 doesn't. Disable this PMIC to avoid the
>>> error in the kernel log caused by an attempt to access it during boot.
>>>
>>> Fixes: f5b788d0e8cd ("arm64: dts: qcom: Add support for X1-based Dell XPS 13 9345")
>>> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
>> Usually we do the opposite: disable nodes by default that may or may not
>> be there and enable them where needed. E.g. for the 4 SMB2360 instances
>> in x1e80100-pmics.dtsi.
>>
>> I think the same approach would also be preferable here. You shouldn't
>> get an error in the log just because you didn't go through all of your
>> DT includes and checked if you really have all of the components listed
>> there. I think it's okay to enable PMICs that are more or less
>> guaranteed to be there, but clearly this is not the case for PM8010.
>>
> That's reasonable. Have there been reports of this error from anyone
> else, or should I go ahead and enable &pm8010 on all !xps13 devices?
Hi all,
Revisiting this change in context of Dell XPS 9345 and now Lenovo
ThinkBook 16 [1] (and upcoming Lenovo Ideapad 5) as these do not have
pm8010.
Perhaps safest and easiest is to simply disable pm8010 in
`x1e80100-pmics.dtsi` as proposed and _not_ enable it on any devices,
since its known to not be used anywhere _yet_? As its a camera PMIC, the
only submitted upstream (did not land yet) change that utilizes pm8010
on X1/X1E is Bryan's CAMSS series that enables camera on CRD [2]. There
are a few other laptops that have patches to enable the camera (my
Zenbook, Bryan's branch on Gitlab for few more laptops) but those were
not submitted yet, so can be easily changed to explicitly enable pm8010
before submission. This way we could simplify this change and not have
to figure out which of the upstream devices do in fact have pm8010 onboard.
On XPS 9345 specifically failure to probe pm8010 leads to power button's
short press not working for shutdown/suspend (only long press kill
laptop power), which is a minor but not irrelevant detail, hence
bringing this up.
Thanks,
Alex
[1]
https://lore.kernel.org/all/20250607-tb16-dt-v6-4-61a31914ee72@oldschoolsolutions.biz/
[2]
https://lore.kernel.org/all/20250417-b4-linux-next-25-03-13-dtsi-x1e80100-camss-v7-5-3fd4124cf35a@linaro.org/
>
> Regards,
> Bjorn
>
next prev parent reply other threads:[~2025-06-15 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 3:17 [PATCH] arm64: dts: qcom: x1e80100-dell-xps13-9345: Disable PM8010 Bjorn Andersson via B4 Relay
2025-03-19 10:06 ` Stephan Gerhold
2025-03-19 11:55 ` Johan Hovold
2025-03-19 14:00 ` Bjorn Andersson
2025-06-15 18:29 ` Aleksandrs Vinarskis [this message]
2025-06-16 8:09 ` Bryan O'Donoghue
2025-06-23 11:37 ` Konrad Dybcio
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=d2eabc30-f1d2-47d8-82f9-86f6f7a705bb@gmail.com \
--to=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurentiu.tudor1@dell.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stephan.gerhold@linaro.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;
as well as URLs for NNTP newsgroup(s).