[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa3f5615-dddf-4c94-88c7-494cf7cd80ab@sirena.org.uk>
Date: Thu, 2 Nov 2023 13:06:51 +0000
From: Mark Brown <broonie@...nel.org>
To: Naresh Solanki <naresh.solanki@...ements.com>
Cc: zev@...ilderbeest.net, Liam Girdwood <lgirdwood@...il.com>,
Patrick Rudolph <patrick.rudolph@...ements.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers/regulator: Notify sysfs about status changes
On Thu, Nov 02, 2023 at 05:35:42PM +0530, Naresh Solanki wrote:
> On Thu, 5 Oct 2023 at 22:30, Mark Brown <broonie@...nel.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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists