From: Mark Brown <broonie@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: zev@bewilderbeest.net, Liam Girdwood <lgirdwood@gmail.com>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/regulator: Notify sysfs about status changes
Date: Thu, 2 Nov 2023 13:06:51 +0000 [thread overview]
Message-ID: <aa3f5615-dddf-4c94-88c7-494cf7cd80ab@sirena.org.uk> (raw)
In-Reply-To: <CABqG17iufSniSLZ2vU5fFduFwV2FL8jNzMcsveOgFUME1jXmgg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Thu, Nov 02, 2023 at 05:35:42PM +0530, Naresh Solanki wrote:
> On Thu, 5 Oct 2023 at 22:30, Mark Brown <broonie@kernel.org> wrote:
> > On Thu, Oct 05, 2023 at 03:30:58PM +0200, Naresh Solanki wrote:
> > We probably should filter the events more, there's events for pre and
> > post voltage change for example which aren't status changes so would be
> > spurious. It ought not to break anything but we should still avoid
> > unneeded work.
> Can you please provide me inputs on the additional filtering needed for this.
> Like some list of events for notify on status?
I think I'd start off with just reporting things that are obviously
errors and not things that should ever go off during normal operation.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-11-02 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 13:30 Naresh Solanki
2023-10-05 17:00 ` Mark Brown
2023-11-02 12:05 ` Naresh Solanki
2023-11-02 13:06 ` Mark Brown [this message]
2023-11-02 14:47 ` Naresh Solanki
2023-11-02 15:01 ` Mark Brown
2023-11-02 15:33 ` Naresh Solanki
2023-11-02 16:50 ` Mark Brown
2023-11-09 10:38 ` Naresh Solanki
2023-11-09 11:31 ` Mark Brown
2023-11-09 15:11 ` Naresh Solanki
2023-11-09 15:21 ` Naresh Solanki
2023-11-13 19:56 ` 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=aa3f5615-dddf-4c94-88c7-494cf7cd80ab@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=zev@bewilderbeest.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 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®