[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJKBP3YR63i4otsf@uf8f119305bce5e.ant.amazon.com>
Date: Tue, 20 Jun 2023 21:49:03 -0700
From: Eduardo Valentin <evalenti@...nel.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Eduardo Valentin <evalenti@...nel.org>, eduval@...zon.com,
linux-pm@...r.kernel.org,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Amit Kucheria <amitk@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 6/7] ythermal: core: report errors to governors
On Tue, Jun 20, 2023 at 07:29:57PM +0200, Rafael J. Wysocki wrote:
>
>
>
> On Fri, May 19, 2023 at 5:27 AM Eduardo Valentin <evalenti@...nel.org> wrote:
> >
> > From: Eduardo Valentin <eduval@...zon.com>
> >
> > Currently the thermal governors are not allowed to
> > react on temperature error events as the thermal core
> > skips the handling and logs an error on kernel buffer.
> > This patch adds the opportunity to report the errors
> > when they happen to governors.
> >
> > Now, if a governor wants to react on temperature read
> > errors, they can implement the .check_error() callback.
>
> Explaining the use case for this would help a lot.
Yeah I agree. I also did not send the full series and will also add
the governor changes for this in the next patch series.
The use case here is primarily when temperature reads can fail.
Common use case, not limited to though, is an I2C device temperature sensor.
While it can be, in many cases, reliable, it is not always guaranteed to
have a successful temperature read. In fact, it is common to see a sporadic
temperature read failure, followed by successful reads.
This patch series will enhance the core to allow temperature update
error communication to the governor so the governor can have the
opportunity to act upon sensor failure.
--
All the best,
Eduardo Valentin
Powered by blists - more mailing lists