From: Nikita Travkin <nikita@trvn.ru>
To: Conor Dooley <conor@kernel.org>
Cc: Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: power: supply: Add pm8916 VM-BMS
Date: Sat, 29 Jul 2023 17:06:14 +0500 [thread overview]
Message-ID: <25e933dc3f28fd73a9b76f172dacfdb2@trvn.ru> (raw)
In-Reply-To: <20230729-facecloth-trembling-3311ca245505@spud>
Conor Dooley писал(а) 29.07.2023 15:03:
> On Fri, Jul 28, 2023 at 10:19:30PM +0500, Nikita Travkin wrote:
>> Qualcomm Voltage Mode BMS is a battery monitoring block in PM8916 PMIC.
>> Document it's DT binding.
>>
>> Signed-off-by: Nikita Travkin <nikita@trvn.ru>
>> ---
>> .../bindings/power/supply/qcom,pm8916-bms-vm.yaml | 64 ++++++++++++++++++++++
>> 1 file changed, 64 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/power/supply/qcom,pm8916-bms-vm.yaml b/Documentation/devicetree/bindings/power/supply/qcom,pm8916-bms-vm.yaml
>> new file mode 100644
>> index 000000000000..455973d46862
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/power/supply/qcom,pm8916-bms-vm.yaml
>> @@ -0,0 +1,64 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/power/supply/qcom,pm8916-bms-vm.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Qualcomm Voltage Mode BMS
>> +
>> +maintainers:
>> + - Nikita Travkin <nikita@trvn.ru>
>> +
>> +description:
>> + Voltage Mode BMS is a hardware block found in some Qualcomm PMICs
>> + such as pm8916. This block performs battery voltage monitoring.
>> +
>> +allOf:
>> + - $ref: power-supply.yaml#
>> +
>> +properties:
>> + compatible:
>> + const: qcom,pm8916-bms-vm
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + items:
>> + - description: FIFO update done
>
> You don't need items: here since you only have one - const: will do.
>
Ack.
>> + interrupt-names:
>> + items:
>> + - const: fifo
>
> Same here, but do you really need a name, when you have only one
> interrupt?
>
Hm, thinking of this more, the hardware actually has more than one
interrupt, even though this one seems to be the only really useful
one. Would a better way forward be to list all of them (and fix
the driver to get the value by it's name) or it would be
acceptable to leave the names here and extend the list at a later
date when (if ever) other interrupts are needed?
Thanks for the review!
Nikita
> Thanks,
> Conor.
>
>> +
>> + monitored-battery: true
>> +
>> + power-supplies: true
>> +
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - interrupt-names
>> + - monitored-battery
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> + pmic {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + battery@4000 {
>> + compatible = "qcom,pm8916-bms-vm";
>> + reg = <0x4000>;
>> + interrupts = <0x0 0x40 4 IRQ_TYPE_EDGE_RISING>;
>> + interrupt-names = "fifo";
>> +
>> + monitored-battery = <&battery>;
>> + power-supplies = <&pm8916_charger>;
>> + };
>> + };
>>
>> --
>> 2.41.0
>>
next prev parent reply other threads:[~2023-07-29 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:19 [PATCH 0/4] Add pm8916 VM-BMS and LBC Nikita Travkin
2023-07-28 17:19 ` [PATCH 1/4] dt-bindings: power: supply: Add pm8916 VM-BMS Nikita Travkin
2023-07-29 10:03 ` Conor Dooley
2023-07-29 12:06 ` Nikita Travkin [this message]
2023-07-29 12:10 ` Conor Dooley
2023-07-29 12:15 ` Nikita Travkin
2023-07-30 10:05 ` Conor Dooley
2023-07-28 17:19 ` [PATCH 2/4] dt-bindings: power: supply: Add pm8916 LBC Nikita Travkin
2023-07-28 17:19 ` [PATCH 3/4] power: supply: Add pm8916 VM-BMS support Nikita Travkin
2023-07-28 17:19 ` [PATCH 4/4] power: supply: Add driver for pm8916 lbc Nikita Travkin
2023-07-29 5:28 ` kernel test robot
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=25e933dc3f28fd73a9b76f172dacfdb2@trvn.ru \
--to=nikita@trvn.ru \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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