From: Guenter Roeck <linux@roeck-us.net>
To: Jonas Rebmann <jre@pengutronix.de>
Cc: Jean Delvare <jdelvare@suse.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
devicetree@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v2 3/3] hwmon: ina238: Add support for INA228
Date: Sat, 19 Jul 2025 15:01:04 -0700 [thread overview]
Message-ID: <1fc421b7-80fc-458b-8ac0-afa61ed03568@roeck-us.net> (raw)
In-Reply-To: <20250718-ina228-v2-3-227feb62f709@pengutronix.de>
On Fri, Jul 18, 2025 at 04:12:50PM +0200, Jonas Rebmann wrote:
> Add support for the Texas Instruments INA228 Ultra-Precise
> Power/Energy/Charge Monitor.
>
> The INA228 is very similar to the INA238 but offers four bits of extra
> precision in the temperature, voltage and current measurement fields.
> It also supports energy and charge monitoring, the latter of which is
> not supported through this patch.
>
> While it seems in the datasheet that some constants such as LSB values
> differ between the 228 and the 238, they differ only for those registers
> where four bits of precision have been added and they differ by a factor
> of 16 (VBUS, VSHUNT, DIETEMP, CURRENT).
>
> Therefore, the INA238 constants are still applicable with regard
> to the bit of the same significance.
>
> Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
Applied.
Thanks,
Guenter
prev parent reply other threads:[~2025-07-19 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 14:12 [PATCH v2 0/3] ina238: Improvements and INA228 support Jonas Rebmann
2025-07-18 14:12 ` [PATCH v2 1/3] hwmon: ina238: Fix inconsistent whitespace Jonas Rebmann
2025-07-19 21:59 ` Guenter Roeck
2025-07-18 14:12 ` [PATCH v2 2/3] dt-bindings: Add INA228 to ina2xx devicetree bindings Jonas Rebmann
2025-07-19 22:00 ` Guenter Roeck
2025-07-18 14:12 ` [PATCH v2 3/3] hwmon: ina238: Add support for INA228 Jonas Rebmann
2025-07-19 22:01 ` Guenter Roeck [this message]
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=1fc421b7-80fc-458b-8ac0-afa61ed03568@roeck-us.net \
--to=linux@roeck-us.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=jre@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®