From: Eduardo Valentin <evalenti@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Eduardo Valentin <evalenti@kernel.org>,
eduval@amazon.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Amit Kucheria <amitk@kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: [PATCH 1/1] thermal: sysfs: avoid actual readings from sysfs
Date: Fri, 30 Jun 2023 18:38:43 -0700 [thread overview]
Message-ID: <ZJ+Do990LVNQx4rp@uf8f119305bce5e.ant.amazon.com> (raw)
In-Reply-To: <2d59de0d-5011-780a-cb6c-94e6e2b74156@linaro.org>
Hey Daniel,
On Fri, Jun 30, 2023 at 12:11:25PM +0200, Daniel Lezcano wrote:
>
>
>
> Hi Rafael,
>
> On 30/06/2023 10:16, Rafael J. Wysocki wrote:
> > On Wed, Jun 28, 2023 at 11:10 PM Eduardo Valentin <evalenti@kernel.org> wrote:
>
> [ ... ]
>
> > So what about adding a new zone attribute that can be used to specify
> > the preferred caching time for the temperature?
> >
> > That is, if the time interval between two consecutive updates of the
> > cached temperature value is less than the value of the new attribute,
> > the cached temperature value will be returned by "temp". Otherwise,
> > it will cause the sensor to be read and the value obtained from it
> > will be returned to user space and cached.
> >
> > If the value of the new attribute is 0, everything will work as it
> > does now (which will also need to be the default behavior).
>
> I'm still not convinced about the feature.
>
> Eduardo provided some numbers but they seem based on the characteristics
> of the I2C, not to a real use case. Eduardo?
Why I2C is not a real use case?
--
All the best,
Eduardo Valentin
next prev parent reply other threads:[~2023-07-01 1:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 0:37 Eduardo Valentin
2023-06-07 6:32 ` Zhang, Rui
2023-06-07 16:28 ` Eduardo Valentin
2023-06-07 9:24 ` Daniel Lezcano
2023-06-07 16:38 ` Eduardo Valentin
2023-06-07 18:23 ` Daniel Lezcano
2023-06-08 17:44 ` Eduardo Valentin
2023-06-12 8:17 ` Daniel Lezcano
2023-06-21 5:06 ` Eduardo Valentin
2023-06-21 11:43 ` Daniel Lezcano
2023-06-22 4:56 ` Eduardo Valentin
2023-06-23 17:31 ` Rafael J. Wysocki
2023-06-28 21:10 ` Eduardo Valentin
2023-06-30 8:16 ` Rafael J. Wysocki
2023-06-30 10:11 ` Daniel Lezcano
2023-06-30 10:46 ` Rafael J. Wysocki
2023-06-30 12:09 ` Daniel Lezcano
2023-07-01 1:49 ` Eduardo Valentin
2023-07-01 7:28 ` Daniel Lezcano
2023-07-05 22:49 ` Eduardo Valentin
2023-07-06 13:22 ` Rafael J. Wysocki
2023-07-07 17:14 ` Eduardo Valentin
2023-07-01 1:38 ` Eduardo Valentin [this message]
2023-07-01 14:20 ` Daniel Lezcano
2023-07-01 1:37 ` Eduardo Valentin
2023-07-06 13:02 ` Rafael J. Wysocki
2023-06-10 17:24 ` Russell Haley
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=ZJ+Do990LVNQx4rp@uf8f119305bce5e.ant.amazon.com \
--to=evalenti@kernel.org \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=eduval@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
/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®