From: Guenter Roeck <linux@roeck-us.net>
To: "Sa, Nuno" <Nuno.Sa@analog.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"jdelvare@suse.com" <jdelvare@suse.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>
Subject: Re: [PATCH 2/3] hwmon: Add support for ltc2947
Date: Thu, 10 Oct 2019 08:21:18 -0700 [thread overview]
Message-ID: <20191010152118.GB4320@roeck-us.net> (raw)
In-Reply-To: <ea52f348c9fab8c9a3c3417909053f4abb12cbcb.camel@analog.com>
On Thu, Oct 10, 2019 at 07:13:06AM +0000, Sa, Nuno wrote:
>
> Quoting the reply I had:
>
> "As the LTC2947 is bi-directional, the most likely use for the Min/Max
> Energy thresholds are for monitoring a battery being charged or
> discharged.
> A limit could be set based around the battery's storage capacity so
> that the battery is protected from being overcharging or fully
> drained."
>
> So, I'm not sure if this is a valid use case for hwmon subsystem. I'm
> aware there's also the power subsystem. So let me know what do you
> prefer here. Should I just report energyX_input attributes? Or can we
> keep the min/max?
>
This isn't really a hwmon use case. Having such min/max attributes would
just be confusing.
Guenter
next prev parent reply other threads:[~2019-10-10 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 12:49 [PATCH 0/3] LTC2947 support Nuno Sá
2019-09-24 12:49 ` [PATCH 1/3] hwmon: Fix HWMON_P_MIN_ALARM mask Nuno Sá
2019-10-02 13:37 ` Guenter Roeck
2019-09-24 12:49 ` [PATCH 2/3] hwmon: Add support for ltc2947 Nuno Sá
2019-10-03 4:14 ` Guenter Roeck
2019-10-04 7:45 ` Sa, Nuno
2019-10-04 15:06 ` Guenter Roeck
2019-10-07 12:25 ` Sa, Nuno
2019-10-07 12:44 ` Guenter Roeck
2019-10-07 14:51 ` Sa, Nuno
2019-10-10 7:13 ` Sa, Nuno
2019-10-10 15:21 ` Guenter Roeck [this message]
2019-10-11 6:59 ` Sa, Nuno
2019-09-24 12:49 ` [PATCH 3/3] dt-bindings: iio: Add ltc2947 documentation Nuno Sá
2019-10-02 14:19 ` Rob Herring
2019-10-02 15:09 ` Sa, Nuno
2019-10-02 19:06 ` Rob Herring
2019-10-04 14:58 ` Sa, Nuno
2019-10-04 15:23 ` Rob Herring
2019-10-08 14:20 ` Sa, Nuno
2019-09-26 10:17 ` [PATCH 0/3] LTC2947 support Sa, Nuno
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=20191010152118.GB4320@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Nuno.Sa@analog.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=mark.rutland@arm.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).