From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
devicetree@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Sebastian Reichel <sre@kernel.org>,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>
Subject: Re: [PATCH 3/3] dt-bindings: power: supply: max17042: describe interrupt
Date: Tue, 17 Aug 2021 17:28:14 -0500 [thread overview]
Message-ID: <YRw3/jDApVGFBfxC@robh.at.kernel.org> (raw)
In-Reply-To: <20210816082716.21193-3-krzysztof.kozlowski@canonical.com>
On Mon, 16 Aug 2021 10:27:16 +0200, Krzysztof Kozlowski wrote:
> The Maxim 17042-family of fuel gauges are often embedded in other Maxim
> chips, e.g. in Maxim 77693 which is a companion power management IC.
> In such designs there might be actually two interrupts:
> - INTB signaling change from charger, flash or MUIC,
> - ALERT signaling change from fuel gauge.
>
> Describe the interrupt in bindings to make it clear it is about the fuel
> gauge ALERT interrupt, not the INT.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
> .../devicetree/bindings/power/supply/maxim,max17042.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-08-17 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 8:27 [PATCH 1/3] power: supply: max17042: handle fails of reading status register Krzysztof Kozlowski
2021-08-16 8:27 ` [PATCH 2/3] power: supply: max17042: remove duplicated STATUS bit defines Krzysztof Kozlowski
2021-08-16 8:27 ` [PATCH 3/3] dt-bindings: power: supply: max17042: describe interrupt Krzysztof Kozlowski
2021-08-17 22:28 ` Rob Herring [this message]
2021-08-16 8:42 ` [PATCH 1/3] power: supply: max17042: handle fails of reading status register Hans de Goede
2021-08-16 11:08 ` Sebastian Reichel
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=YRw3/jDApVGFBfxC@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.krzyszkowiak@puri.sm \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.