From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Nikita Travkin <nikita@trvn.ru>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v2 2/3] arm64: dts: qcom: pm8916: Add BMS and charger
Date: Thu, 26 Oct 2023 22:03:43 +0200 [thread overview]
Message-ID: <e56bec85-46be-4c88-ae88-199e7272ccdd@linaro.org> (raw)
In-Reply-To: <ZTq7XGz4Ux8lYQho@gerhold.net>
On 10/26/23 21:17, Stephan Gerhold wrote:
> On Thu, Oct 26, 2023 at 08:54:00PM +0200, Konrad Dybcio wrote:
>> On 10/24/23 11:29, Nikita Travkin wrote:
>>> Konrad Dybcio писал(а) 24.10.2023 13:34:
>>>> On 10/23/23 08:20, Nikita Travkin wrote:
>>>>> pm8916 contains some hardware blocks for battery powered devices:
>>>>>
>>>>> - VM-BMS: Battery voltage monitoring block.
>>>>> - LBC: Linear battery charger.
>>>>>
>>>>> Add them to the pmic dtsi so the devices that make use of those blocks
>>>>> can enable them.
>>>>>
>>>>> Signed-off-by: Nikita Travkin <nikita@trvn.ru>
>>>>> ---
>>>>> arch/arm64/boot/dts/qcom/pm8916.dtsi | 48 ++++++++++++++++++++++++++++++++++++
>>>>> 1 file changed, 48 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/qcom/pm8916.dtsi b/arch/arm64/boot/dts/qcom/pm8916.dtsi
>>>>> index f4de86787743..4b2e8fb47d2d 100644
>>>>> --- a/arch/arm64/boot/dts/qcom/pm8916.dtsi
>>>>> +++ b/arch/arm64/boot/dts/qcom/pm8916.dtsi
>>>>> @@ -41,6 +41,35 @@ watchdog {
>>>>> };
>>>>> };
>>>>> + pm8916_charger: charger@1000 {
>>>>> + compatible = "qcom,pm8916-lbc";
>>>>> + reg = <0x1000>, <0x1200>, <0x1300>, <0x1600>;
>>>>> + reg-names = "chgr", "bat_if", "usb", "misc";
>>>>> +
>>>>> + interrupts = <0x0 0x10 0 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x10 5 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x10 6 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x10 7 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x12 0 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x12 1 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x13 0 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x13 1 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x13 2 IRQ_TYPE_EDGE_BOTH>,
>>>>> + <0x0 0x13 4 IRQ_TYPE_EDGE_BOTH>;
>>>>> + interrupt-names = "vbat_det",
>>>>> + "fast_chg",
>>>>> + "chg_fail",
>>>>> + "chg_done",
>>>>> + "bat_pres",
>>>>> + "temp_ok",
>>>>> + "coarse_det",
>>>>> + "usb_vbus",
>>>> So, both the charger and the USBIN driver use the same irq? :/
>>>>
>>>
>>> AFAIU the usbin extcon driver pretty much just tracks the state
>>> of the IRQ to report extcon. It happens to assume the same part
>>> of the pmic though, yes, which also means there will be no user
>>> that would enable both charger and vbus extcon, since charger
>>> driver provides this functionality as well.
>> So, should USBIN be removed from PM8916 dt since it's essentially
>> a part of the charger block?
>>
>
> The "USB_IN" pad of the PM8916 seems to be connected on pretty much all
> devices, even if they are using external chargers and the charging
> functionality of PM8916 is completely disabled. For those devices, the
> &pm8916_usbin device provides a convenient way to detect the USB state,
> even without a working charger driver.
>
> While we could modify the PM8916 charger driver and DT node to have some
> special mode where charging and battery monitoring is completely
> disabled and only the USBIN extcon is provided, I'm not sure if that
> would provide a significant advantage compared to just keeping the
> simple &pm8916_usbin node with the existing driver.
Hmm okay I see..
Generally it's rather "no bueno" to have two DT nodes consuming the
same register space.. What happens when you enable BMS on a device
with a non-PM8916 charger? Does it correctly recognize "no battery"
etc.?
Konrad
next prev parent reply other threads:[~2023-10-26 20:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 6:20 [PATCH v2 0/3] pm8916: Add BMS and charger Nikita Travkin
2023-10-23 6:20 ` [PATCH v2 1/3] dt-bindings: mfd: qcom,spmi-pmic: Add pm8916 vm-bms and lbc Nikita Travkin
2023-10-23 17:40 ` Rob Herring
2023-10-24 5:08 ` Nikita Travkin
2023-10-25 12:21 ` Lee Jones
2023-10-25 12:57 ` Nikita Travkin
2023-10-27 7:14 ` Krzysztof Kozlowski
2023-10-25 15:44 ` (subset) " Lee Jones
2023-10-27 7:20 ` Krzysztof Kozlowski
2023-10-31 7:54 ` Lee Jones
2023-11-14 5:24 ` Nikita Travkin
2023-11-14 15:22 ` Krzysztof Kozlowski
2023-10-23 6:20 ` [PATCH v2 2/3] arm64: dts: qcom: pm8916: Add BMS and charger Nikita Travkin
2023-10-24 8:34 ` Konrad Dybcio
2023-10-24 9:29 ` Nikita Travkin
2023-10-26 18:54 ` Konrad Dybcio
2023-10-26 19:17 ` Stephan Gerhold
2023-10-26 20:03 ` Konrad Dybcio [this message]
2023-10-27 5:44 ` Nikita Travkin
2023-10-31 11:20 ` Konrad Dybcio
2023-10-23 6:20 ` [PATCH v2 3/3] arm64: dts: qcom: msm8916-longcheer-l8150: Add battery " Nikita Travkin
2023-10-24 8:33 ` Konrad Dybcio
2023-10-24 9:33 ` Nikita Travkin
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=e56bec85-46be-4c88-ae88-199e7272ccdd@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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