From: "Nuno Sá" <noname.nuno@gmail.com>
To: Conor Dooley <conor@kernel.org>, Nuno Sa <nuno.sa@analog.com>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v4 1/3] dt-bindings: hwmon: Add LTC4282 bindings
Date: Wed, 20 Dec 2023 09:48:40 +0100 [thread overview]
Message-ID: <32be5cae6429076d07bc944f4e1db379ba490361.camel@gmail.com> (raw)
In-Reply-To: <20231219-cusp-bottom-f96757a74ad4@spud>
On Tue, 2023-12-19 at 16:39 +0000, Conor Dooley wrote:
> On Mon, Dec 18, 2023 at 05:29:42PM +0100, Nuno Sa wrote:
> > Add bindings for the LTC4282 High Current Hot Swap Controller with I2C
> > Compatible Monitoring.
>
> I'm not sure what to look for to confirm that the gpio2/gpio3 muxing was
> fixed in this version, but the default stuff was fixed, so on that basis
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
Thanks for the ack...
The muxing is fixed by adding the new 'adi,gpio3-monitor-enable' property.
That's how we mux gpio3 into the ADC (so that pin is monitored as part of
hwmon). Note that if that property is given, I'm restricting the gpio2 allowed
values to 'stress_fet' because we can't mux both pins.
- Nuno Sá
next prev parent reply other threads:[~2023-12-20 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 16:29 [PATCH v4 0/3] Add support for LTC4282 Nuno Sa
2023-12-18 16:29 ` [PATCH v4 1/3] dt-bindings: hwmon: Add LTC4282 bindings Nuno Sa
2023-12-19 16:39 ` Conor Dooley
2023-12-20 8:48 ` Nuno Sá [this message]
2023-12-18 16:29 ` [PATCH v4 2/3] hwmon: add fault attribute for voltage channels Nuno Sa
2023-12-18 16:29 ` [PATCH v4 3/3] hwmon: ltc4282: add support for the LTC4282 chip Nuno Sa
2024-01-09 12:19 ` [PATCH v4 0/3] Add support for LTC4282 Nuno Sá
2024-01-09 15:17 ` Krzysztof Kozlowski
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=32be5cae6429076d07bc944f4e1db379ba490361.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nuno.sa@analog.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).