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:15:06 +0500 [thread overview]
Message-ID: <0b41a93ee82674e65a3801f5a37edd5a@trvn.ru> (raw)
In-Reply-To: <20230729-splatter-garland-495a414c323e@spud>
Conor Dooley писал(а) 29.07.2023 17:10:
> On Sat, Jul 29, 2023 at 05:06:14PM +0500, Nikita Travkin wrote:
>> Conor Dooley писал(а) 29.07.2023 15:03:
>> > On Fri, Jul 28, 2023 at 10:19:30PM +0500, Nikita Travkin wrote:
>
>> >> + 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
>
> Yes.
>
>> (and fix
>> the driver to get the value by it's name)
>
> It's not a fix to do that, the order of the interrupts is not variable,
> so there's nothing wrong with using the indices. You can do it if you
> like.
>
>> 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?
>
> If you know what they are, please describe them now, even if the driver
> does not use them (yet).
>
Thanks for the clarification! Will make sure both drivers have all
interrupts described in v2
Nikita
> Thanks,
> Conor.
next prev parent reply other threads:[~2023-07-29 12:15 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
2023-07-29 12:10 ` Conor Dooley
2023-07-29 12:15 ` Nikita Travkin [this message]
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=0b41a93ee82674e65a3801f5a37edd5a@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