From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Naresh Solanki <naresh.solanki@9elements.com>,
linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
linux-kernel@vger.kernel.org, Sascha Hauer <sha@pengutronix.de>,
jerome Neanne <jneanne@baylibre.com>,
"Mutanen, Mikko" <Mikko.Mutanen@fi.rohmeurope.com>
Subject: Re: [PATCH v2 2/3] hwmon: (pmbus/core): Add regulator event support
Date: Tue, 11 Apr 2023 12:12:30 +0300 [thread overview]
Message-ID: <80b09e1b-f00e-4c78-6627-111959779376@gmail.com> (raw)
In-Reply-To: <d6a3ca82-7245-45e1-b8ff-a9970671b04f@sirena.org.uk>
On 4/6/23 16:43, Mark Brown wrote:
> On Thu, Apr 06, 2023 at 11:00:02AM +0300, Matti Vaittinen wrote:
>> ke 5. huhtik. 2023 klo 18.19 Mark Brown (broonie@kernel.org) kirjoitti:
>>> On Wed, Apr 05, 2023 at 07:18:32AM -0700, Guenter Roeck wrote:
>> Or, is it so that no "generic handling" of these errors is to be
>> expected? Eg, consumers who implement any handling must always be
>> targeted to a very specific system? My thinking has been that the
>> device sending the notification knows the severity of the problem and
>> - for example the REGULATOR_EVENT_REGULATION_OUT is only sent with
>> such severe problems that consumers can try disabling the regulator,
>> whereas the _WARN level notifications may not warrant such action. But
>> again, I don't think we have a specification for this - so this is
>> just my thinking - which may be off.
>
> Do we actually have practical examples of systems sending warnings that
> aren't followed in very short order by more severe errors, notified or
> otherwise?
I asked about this from the hardware colleague(s) in Japan. This far
they were not able to provide me a concrete information.
One potential example use-case they mentioned was "rejecting and
re-doing a measurement if regulator warnings are flagged". This sounds
(to me) like using a voltage from a regulator as some measurement
reference or supply, with very strict warning limits. Still, as said, I
did not have a concrete example if/where this is actually implemented -
which means the answer to your question remains still "no".
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2023-04-11 9:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 15:03 [PATCH v2 1/3] hwmon: (pmbus/core): Add rdev in pmbus_data struct Naresh Solanki
2023-03-28 15:03 ` [PATCH v2 2/3] hwmon: (pmbus/core): Add regulator event support Naresh Solanki
2023-03-29 6:48 ` Matti Vaittinen
2023-04-05 13:15 ` Guenter Roeck
2023-04-05 13:57 ` Matti Vaittinen
2023-04-05 14:18 ` Guenter Roeck
2023-04-05 15:19 ` Mark Brown
2023-04-06 8:00 ` Matti Vaittinen
2023-04-06 13:43 ` Mark Brown
2023-04-10 8:19 ` Matti Vaittinen
2023-04-10 14:40 ` Guenter Roeck
2023-04-10 16:53 ` Matti Vaittinen
2023-04-10 17:47 ` Guenter Roeck
2023-04-11 6:10 ` Matti Vaittinen
2023-04-11 11:08 ` Mark Brown
2023-04-11 12:07 ` Mark Brown
2023-04-12 8:12 ` Matti Vaittinen
2023-04-11 9:12 ` Matti Vaittinen [this message]
2023-04-12 15:13 ` Guenter Roeck
2023-03-28 15:03 ` [PATCH v2 3/3] hwmon: (pmbus/core): Notify regulator events Naresh Solanki
2023-04-12 15:16 ` Guenter Roeck
2023-04-12 15:12 ` [PATCH v2 1/3] hwmon: (pmbus/core): Add rdev in pmbus_data struct 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=80b09e1b-f00e-4c78-6627-111959779376@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=Mikko.Mutanen@fi.rohmeurope.com \
--cc=broonie@kernel.org \
--cc=jdelvare@suse.com \
--cc=jneanne@baylibre.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=sha@pengutronix.de \
/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).