From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Eric Gonçalves" <ghatto404@gmail.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: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: dts: qcom: r0q: enable max77705 PMIC
Date: Wed, 8 Oct 2025 10:34:00 +0200 [thread overview]
Message-ID: <823af9ee-df4e-40de-bf30-084442bb1d2c@oss.qualcomm.com> (raw)
In-Reply-To: <BB4E3024-F897-452B-9D3F-250ED2D52195@gmail.com>
On 9/26/25 4:19 AM, Eric Gonçalves wrote:
>
>
> On September 25, 2025 10:06:53 AM GMT-03:00, Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
>> On 9/20/25 3:46 AM, Eric Gonçalves wrote:
>>> The Samsung Galaxy S22 uses max77705 as its charger, fuelgauge and haptic
>>> PMIC, enable the fuelgauge and charger for now.
>>>
>>> Signed-off-by: Eric Gonçalves <ghatto404@gmail.com>
>>> ---
>>
>> [...]
>>
>>> +&i2c5 {
>>> + status = "okay";
>>> +
>>> + max77705_charger: charger@69 {
>>> + compatible = "maxim,max77705-charger";
>>> + reg = <0x69>;
>>
>> Please use tabs consistently
> Sure
>>
>>> + monitored-battery = <&battery>;
>>> + interrupt-parent = <&tlmm>;
>>> + interrupts = <5 IRQ_TYPE_LEVEL_LOW>;
>>
>> interrupts-extended = <&tlmm 5 IRQ...>, here and below
> why extended?
>>
>>> + };
>>> +
>>> + fuel-gauge@36 {
>>> + reg = <0x36>;
>>
>> sorting by unit address is welcome
> Sure
>>
>>> + compatible = "maxim,max77705-battery";
>>> + power-supplies = <&max77705_charger>;
>>> + interrupt-parent = <&tlmm>;
>>> + interrupts = <5 IRQ_TYPE_LEVEL_LOW>;
>>> + };
>>
>> These nodes should be children of "maxim,max77705"
>> (see drivers/mfd/max77705.c)
> What do you mean by this? I looked at the driver,
> should I add the pmic@66 node and put
> the units inside of it? Because starqltechn doesn't do that and
> places them outside. Also, by adding the
> pmic@66
> node it expects to have led/haptics nodes as well.
Well, the chip comes as a single package, so this only makes sense
and the bindings (mfd/maxim,max77705.yaml) corroborate that.
Just looking at the YAML, you should be able to omit the LED part
if it's not connected anywhere
Konrad
next prev parent reply other threads:[~2025-10-08 8:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 1:46 [PATCH 0/5] arm64: dts: qcom: r0q: enable more peripherals Eric Gonçalves
2025-09-20 1:46 ` [PATCH 1/5] arm64: dts: qcom: r0q: add gpio keys Eric Gonçalves
2025-09-20 15:45 ` Dmitry Baryshkov
2025-09-20 18:02 ` Eric Gonçalves
2025-09-20 20:15 ` Dmitry Baryshkov
2025-09-20 20:22 ` Eric Gonçalves
2025-09-20 23:21 ` Dmitry Baryshkov
2025-09-20 1:46 ` [PATCH 2/5] arm64: dts: qcom: r0q: add touchscreen support Eric Gonçalves
2025-09-20 15:46 ` Dmitry Baryshkov
2025-09-25 13:08 ` Konrad Dybcio
2025-09-25 21:37 ` Eric Gonçalves
2025-09-20 1:46 ` [PATCH 3/5] arm64: dts: qcom: r0q: enable max77705 PMIC Eric Gonçalves
2025-09-20 15:48 ` Dmitry Baryshkov
2025-09-20 18:04 ` Eric Gonçalves
2025-09-25 13:06 ` Konrad Dybcio
2025-09-26 2:19 ` Eric Gonçalves
2025-10-08 8:34 ` Konrad Dybcio [this message]
2025-10-09 20:31 ` Eric Gonçalves
2025-10-20 12:06 ` Konrad Dybcio
2025-09-20 1:46 ` [PATCH 4/5] arm64: dts: qcom: r0q: enable hardware clocks Eric Gonçalves
2025-09-25 13:09 ` Konrad Dybcio
2025-10-05 3:50 ` Eric Gonçalves
2025-10-06 12:31 ` Konrad Dybcio
2025-10-06 15:49 ` Eric Gonçalves
2025-10-08 8:48 ` Konrad Dybcio
2025-10-09 19:20 ` Eric Gonçalves
2025-09-20 1:46 ` [PATCH 5/5] arm64: dts: qcom: r0q: enable ufs storage Eric Gonçalves
2025-09-20 20:16 ` Dmitry Baryshkov
2025-09-25 13:07 ` Konrad Dybcio
2025-09-25 21:37 ` Eric Gonçalves
2025-10-06 12:08 ` Konrad Dybcio
2025-10-06 15:49 ` Eric Gonçalves
2025-09-22 17:27 ` [PATCH 0/5] arm64: dts: qcom: r0q: enable more peripherals Rob Herring (Arm)
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=823af9ee-df4e-40de-bf30-084442bb1d2c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghatto404@gmail.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;
as well as URLs for NNTP newsgroup(s).