From: "Nuno Sá" <noname.nuno@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>, nuno.sa@analog.com
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v3 2/2] hwmon: ltc4282: add support for the LTC4282 chip
Date: Wed, 13 Dec 2023 15:44:23 +0100 [thread overview]
Message-ID: <114c8347063d196b58f48bb5ce9914144e215c4b.camel@gmail.com> (raw)
In-Reply-To: <505ac1bf-616a-443d-b2bc-a54b3c193757@roeck-us.net>
On Wed, 2023-12-13 at 06:35 -0800, Guenter Roeck wrote:
> On 12/13/23 02:06, Nuno Sá wrote:
> [ ... ]
> > >
> > > We could also use in[01]_reset_history. While that is originally intended to
> > > reset
> > > min/max voltage history, I think it makes sense to extend the meaning to
> > > include
> > > fault history (even more so if that history includes over/undervoltage events).
> > > Plus, there are other _reset_history attributes which could be used to reset
> > > power/current/temperature history separately if that is supported by the chip.
> > >
> >
> > Well, I'm already supporting _reset_history in the voltage/power/current channels
> > so
> > I can easily extend that for clearing fault history if that is fine with you. I
> > just
> > need to document it because it's a bit of an "hidden" thing. The question would
> > also
> > be, should I just document this for this chip docs or in the general hwmon docs?
> >
>
> I'd say chip specific for now. We can document it in the general documentation
> if/when we get more chips with the same characteristics.
>
Agreed... Alright, I think I have now all I need to work on v4.
Thanks!
- Nuno Sá
next prev parent reply other threads:[~2023-12-13 14:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 15:22 [PATCH v3 0/2] Add support for LTC4282 Nuno Sa
2023-12-05 15:22 ` Nuno Sa via B4 Relay
2023-12-05 15:22 ` [PATCH v3 1/2] dt-bindings: hwmon: Add LTC4282 bindings Nuno Sa
2023-12-05 15:22 ` Nuno Sa via B4 Relay
2023-12-05 16:18 ` Conor Dooley
2023-12-06 8:38 ` Nuno Sá
2023-12-06 15:41 ` Conor Dooley
2023-12-05 15:22 ` [PATCH v3 2/2] hwmon: ltc4282: add support for the LTC4282 chip Nuno Sa
2023-12-05 15:22 ` Nuno Sa via B4 Relay
2023-12-11 15:36 ` Guenter Roeck
2023-12-12 14:28 ` Nuno Sá
2023-12-12 15:14 ` Guenter Roeck
2023-12-12 15:30 ` Nuno Sá
2023-12-12 17:59 ` Guenter Roeck
2023-12-13 10:06 ` Nuno Sá
2023-12-13 14:35 ` Guenter Roeck
2023-12-13 14:44 ` Nuno Sá [this message]
2023-12-11 15:41 ` Guenter Roeck
2023-12-12 13:53 ` Nuno Sá
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=114c8347063d196b58f48bb5ce9914144e215c4b.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nuno.sa@analog.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 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.