From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: "Aiqun Yu (Maria)" <quic_aiquny@quicinc.com>
Cc: 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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Abel Vesa <abel.vesa@linaro.org>,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: x1e80100-pmics: Enable all SMB2360 separately
Date: Tue, 10 Dec 2024 09:25:28 +0100 [thread overview]
Message-ID: <Z1f6-G5fXr-383IK@linaro.org> (raw)
In-Reply-To: <01d0b807-6201-43fb-8286-df04d722610f@quicinc.com>
On Sat, Dec 07, 2024 at 11:57:54PM +0800, Aiqun Yu (Maria) wrote:
> On 12/4/2024 12:27 AM, Stephan Gerhold wrote:
> > At the moment, x1e80100-pmics.dtsi enables two of the SMB2360 PMICs by
> > default and only leaves the third disabled. This was introduced in commit
>
> One correction: it’s not only the third PMIC that is disabled. Both the
> third (smb2360_2) and fourth (smb2360_3) are disabled. This information
> is verified from link[1]:
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi
>
You're right, I didn't realize there can be a fourth SMB2360 at all. :-)
It doesn't change anything for the patch itself, but I'll fix the commit
message in v2 just to avoid any confusion.
Thanks,
Stephan
prev parent reply other threads:[~2024-12-10 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 16:27 [PATCH] arm64: dts: qcom: x1e80100-pmics: Enable all SMB2360 separately Stephan Gerhold
2024-12-07 15:57 ` Aiqun Yu (Maria)
2024-12-10 8:25 ` Stephan Gerhold [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=Z1f6-G5fXr-383IK@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@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=quic_aiquny@quicinc.com \
--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