From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: jdelvare@suse.com, linux@roeck-us.net, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, corbet@lwn.net,
wenliang202407@163.com, jre@pengutronix.de
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v3 0/4] hwmon: Add support for INA780
Date: Fri, 29 Aug 2025 15:05:08 +1200 [thread overview]
Message-ID: <20250829030512.1179998-1-chris.packham@alliedtelesis.co.nz> (raw)
This series adds support for the INA780 to the existing ina238.c driver.
v2: https://lore.kernel.org/linux-hwmon/20250808030510.552724-1-chris.packham@alliedtelesis.co.nz/
v1: https://lore.kernel.org/linux-hwmon/20250806005127.542298-1-chris.packham@alliedtelesis.co.nz/
One important bit of feedback I've not addressed is this
> Follow-up: I ordered evaluation boards for INA228, INA237, INA238, and INA780A.
> I'll want to see support added for current limits on all chips, using a similar
> approach as the one in the ina2xx driver. After all, the shunt voltage limits
> are really current limits in disguise. With that and appropriate chip specific
> parameters the differences between the chips should become relatively minor.
>
> This should also simplify adding support for INA700 which seems similar to INA780A.
I wasn't sure if that meant you were going to look at adding current limits to
the existing chips and I should wait or if you wanted me to try based on the
code. Given our timezone differences I figured I'd send the series anyway.
Patch 2 is a bugfix that you might want to pick up sooner.
Chris Packham (4):
dt-bindings: hwmon: ti,ina2xx: Add INA780 device
hwmon: (ina238) Correctly clamp temperature
hwmon: (ina238) Add ina238_config fields
hwmon: (ina238) Add support for INA780
.../devicetree/bindings/hwmon/ti,ina2xx.yaml | 1 +
Documentation/hwmon/ina238.rst | 20 ++
drivers/hwmon/ina238.c | 273 ++++++++++++++----
3 files changed, 238 insertions(+), 56 deletions(-)
--
2.51.0
next reply other threads:[~2025-08-29 3:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 3:05 Chris Packham [this message]
2025-08-29 3:05 ` [PATCH v3 1/4] dt-bindings: hwmon: ti,ina2xx: Add INA780 device Chris Packham
2025-08-31 22:35 ` Guenter Roeck
2025-08-29 3:05 ` [PATCH v3 2/4] hwmon: (ina238) Correctly clamp temperature Chris Packham
2025-08-29 9:55 ` Guenter Roeck
2025-08-31 21:12 ` Chris Packham
2025-08-31 22:09 ` Guenter Roeck
2025-08-31 22:34 ` Guenter Roeck
2025-08-29 3:05 ` [PATCH v3 3/4] hwmon: (ina238) Add ina238_config fields Chris Packham
2025-08-29 15:56 ` Guenter Roeck
2025-08-29 3:05 ` [PATCH v3 4/4] hwmon: (ina238) Add support for INA780 Chris Packham
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=20250829030512.1179998-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=jre@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=wenliang202407@163.com \
/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).