From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Hardware Monitoring <linux-hwmon@vger.kernel.org>,
Loic Guegan <loic.guegan@mailbox.org>
Subject: Re: [PATCH 2/2] hwmon: (ina260) Add support for INA260
Date: Thu, 19 Sep 2024 08:30:39 +0000 [thread overview]
Message-ID: <ZuvhL4UbK5MvO67C@google.com> (raw)
In-Reply-To: <20240913003145.1931634-2-linux@roeck-us.net>
On Thu, Sep 12, 2024 at 05:31:45PM -0700, Guenter Roeck wrote:
> INA260 is similar to other chips of the series, except it has an internal
> shunt resistor. The calibration register is therefore not present. Also,
> the current register address was changed, though that does not matter for
> the driver since the shunt voltage register (which is now the current
> register) value is already used to read the current.
>
> Cc: Loic Guegan <loic.guegan@mailbox.org>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Tzung-Bi Shih <tzungbi@kernel.org>
> @@ -157,6 +160,7 @@ static const struct ina2xx_config ina2xx_config[] = {
> .bus_voltage_lsb = 4000,
> .power_lsb_factor = 20,
> .has_alerts = false,
> + .has_ishunt = false,
> },
> [ina226] = {
> .config_default = INA226_CONFIG_DEFAULT,
> @@ -166,6 +170,16 @@ static const struct ina2xx_config ina2xx_config[] = {
> .bus_voltage_lsb = 1250,
> .power_lsb_factor = 25,
> .has_alerts = true,
> + .has_ishunt = false,
No strong preference: or just don't set them.
next prev parent reply other threads:[~2024-09-19 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 0:31 [PATCH 1/2] hwmon: (ina2xx) Add support for has_alerts configuration flag Guenter Roeck
2024-09-13 0:31 ` [PATCH 2/2] hwmon: (ina260) Add support for INA260 Guenter Roeck
2024-09-19 8:30 ` Tzung-Bi Shih [this message]
2024-09-19 8:30 ` [PATCH 1/2] hwmon: (ina2xx) Add support for has_alerts configuration flag Tzung-Bi Shih
2024-09-19 14:35 ` Guenter Roeck
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=ZuvhL4UbK5MvO67C@google.com \
--to=tzungbi@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=loic.guegan@mailbox.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.