From: Mark Brown <broonie@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Marcello Sylvester Bauer <sylv@sylv.io>
Subject: Re: [PATCH 3/5] regulator: max597x: Add support for max597x regulator
Date: Tue, 19 Jul 2022 18:04:08 +0100 [thread overview]
Message-ID: <YtbkCJQCXEiB7wlM@sirena.org.uk> (raw)
In-Reply-To: <CABqG17gL=7TJHNowpM8OJD4Pmezp5iVmAKx4csmakrTpp5bUkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Tue, Jul 19, 2022 at 09:29:15PM +0530, Naresh Solanki wrote:
> > I like the way the IRQ helpers have been used here. It'd be cool to hear
> > how the rest of the system you're dealing with utilize the WARN level
> > events :)
> Userspace applications would receive sysfs notify for these events in realtime
> (there is another patch that enables sysfs notify on regulator events)
> This will enable taking necessary action if the regulator is not in good state.
Right, the question is more what the action that might be taken is.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-19 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 12:22 [PATCH 1/5] dt-bindings: mfd: Add bindings for MAX5970 and MAX5978 Naresh Solanki
2022-07-05 12:22 ` [PATCH 2/5] mfd: max597x: Add support " Naresh Solanki
2022-07-05 12:22 ` [PATCH 3/5] regulator: max597x: Add support for max597x regulator Naresh Solanki
2022-07-12 7:30 ` Matti Vaittinen
2022-07-19 15:59 ` Naresh Solanki
2022-07-19 17:04 ` Mark Brown [this message]
2022-07-05 12:22 ` [PATCH 4/5] iio: max597x: Add support for max597x Naresh Solanki
2022-07-05 12:22 ` [PATCH 5/5] leds: " Naresh Solanki
2022-07-17 12:43 ` Pavel Machek
2022-07-06 10:17 ` (subset) [PATCH 1/5] dt-bindings: mfd: Add bindings for MAX5970 and MAX5978 Mark Brown
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=YtbkCJQCXEiB7wlM@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=sylv@sylv.io \
/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
all inboxes | Powered by JetHome®