From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Manaf Meethalavalappu Pallikunhi
<manaf.pallikunhi@oss.qualcomm.com>
Cc: Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-hwmon@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
mfd@lists.linux.dev, Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Subject: Re: [PATCH v2 01/10] dt-bindings: hwmon: Describe Qualcomm BCL hardware
Date: Thu, 30 Jul 2026 13:35:00 +0200 [thread overview]
Message-ID: <63b4c911-d1a4-42b0-a66f-b0c84308d5dc@oss.qualcomm.com> (raw)
In-Reply-To: <20260723-radiant-scorpion-of-hurricane-cbed57@quoll>
Hi Krzystof,
On 7/23/26 10:11, Krzysztof Kozlowski wrote:
> On Wed, Jul 22, 2026 at 12:00:06AM +0530, Manaf Meethalavalappu Pallikunhi wrote:
>> +properties:
>> + compatible:
>> + enum:
>> + - qcom,pm7250b-bcl
>> + - qcom,pm8350c-bcl
>> + - qcom,pm8550-bcl
>> + - qcom,pmh0101-bcl
>> + - qcom,pmih0108-bcl
>> + - qcom,smb2360-bcl
>> + - qcom,smb2370-bcl
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 2
>> +
>> + interrupt-names:
>> + items:
>> + - const: max-min
>> + - const: critical
>> +
>
> Binding looks in general ok, but feels incomplete. If this is battery
> limiting hardware, does it actually need any battery data through
> monitored-battery property?
I'm not sure it is relevant here. The BCL is not a power supply neither
a charger. It monitors a power supply output which can be a battery or
another source of power AFAIU.
The monitored-battery property is used by chargers or fuel gauges if I
refer to the documentation.
The BCL monitors the output of the power supply while the chargers
monitors the input for the battery.
Manaf, does it sound correct ?
next prev parent reply other threads:[~2026-07-30 11:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 18:30 [PATCH v2 00/10] hwmon: Add Qualcomm SPMI BCL driver Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 01/10] dt-bindings: hwmon: Describe Qualcomm BCL hardware Manaf Meethalavalappu Pallikunhi
2026-07-23 8:11 ` Krzysztof Kozlowski
2026-07-30 11:35 ` Daniel Lezcano [this message]
2026-07-30 15:19 ` Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 02/10] hwmon: Add Qualcomm PMIC BCL driver Manaf Meethalavalappu Pallikunhi
2026-07-21 20:44 ` Guenter Roeck
2026-07-22 17:38 ` Manaf Meethalavalappu Pallikunhi
2026-07-22 17:46 ` Guenter Roeck
2026-07-22 18:19 ` Manaf Meethalavalappu Pallikunhi
2026-07-22 18:59 ` Guenter Roeck
2026-07-23 19:16 ` Manaf Meethalavalappu Pallikunhi
2026-07-24 0:04 ` Guenter Roeck
2026-07-30 11:48 ` Daniel Lezcano
2026-07-30 15:17 ` Guenter Roeck
2026-08-13 19:27 ` Manaf Meethalavalappu Pallikunhi
2026-08-13 19:54 ` Guenter Roeck
2026-07-23 6:29 ` Uwe Kleine-König
2026-07-23 7:40 ` Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 03/10] arm64: dts: qcom: pm7250b: Enable BCL sensor node Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 04/10] arm64: dts: qcom: hamoa-pmic: " Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 05/10] arm64: dts: qcom: pm8350c: " Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 06/10] arm64: dts: qcom: pmh0101: " Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 07/10] arm64: dts: qcom: pm8550: " Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 08/10] arm64: dts: qcom: pmih0108-kaanapali: " Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 09/10] arm64: dts: qcom: pmih0108: " Manaf Meethalavalappu Pallikunhi
2026-07-21 18:30 ` [PATCH v2 10/10] arm64: dts: qcom: smb2370: " Manaf Meethalavalappu Pallikunhi
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=63b4c911-d1a4-42b0-a66f-b0c84308d5dc@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gaurav.kohli@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=manaf.pallikunhi@oss.qualcomm.com \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sboyd@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
all inboxes | Powered by JetHome®