From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] hwmon: (ina3221) Add summation feature support
Date: Mon, 21 Oct 2019 01:12:12 -0700 [thread overview]
Message-ID: <20191021081211.GA5684@Asurada> (raw)
In-Reply-To: <20191020163628.GA16363@roeck-us.net>
On Sun, Oct 20, 2019 at 09:36:28AM -0700, Guenter Roeck wrote:
> On Wed, Oct 16, 2019 at 04:57:02PM -0700, Nicolin Chen wrote:
> > This patch implements the summation feature of INA3221, mainly the
> > SCC (enabling) and SF (warning flag) bits of MASK_ENABLE register,
> > INA3221_SHUNT_SUM (summation of shunt voltages) register, and the
> > INA3221_CRIT_SUM (its critical alert setting) register.
> >
> > Although the summation feature allows user to select which channels
> > to be added to the result, as an initial support, this patch simply
> > selects all channels by default, with one only condition: all shunt
> > resistor values need to be the same. This is because the summation
> > of current channels can be only accurately calculated, using shunt
> > voltage sum register, if all shunt resistors are equivalent.
> >
> > Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com>
> > ---
> >
> > Hi Guenter,
> >
> > I know my previous questions haven't been answered yet, so nodes
> > for enabling bits aren't decided completely. But this patch only
> > adds voltage and its current, and we had a conclusion for these
> > two already last time. So I think we may add them first. Thanks!
> >
>
> I don't really like the term "summation", as it is the process of
> summing things up, not the result. I'll change "summation of" in
> the documentation to "sum of" and apply the patch.
Thank you!
prev parent reply other threads:[~2019-10-21 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 23:57 [PATCH] hwmon: (ina3221) Add summation feature support Nicolin Chen
2019-10-20 16:36 ` Guenter Roeck
2019-10-21 8:12 ` Nicolin Chen [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=20191021081211.GA5684@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.