X86 platform drivers
 help / color / mirror / Atom feed
From: Benjamin Berg <bberg@redhat.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
	"Barnabás Pőcze" <pobrn@protonmail.com>
Cc: Elia Devito <eliadevito@gmail.com>,
	Mark Pearson <mpearson@lenovo.com>,
	Bastien Nocera <hadess@hadess.net>,
	Jared Dominguez <jaredz@redhat.com>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: RFC: offering a standardized (/sys/class) userspace API for selecting system/laptop performance-profiles
Date: Thu, 17 Sep 2020 15:59:07 +0200	[thread overview]
Message-ID: <0470605070bdce679e91aaa1523fe0cb94becc49.camel@redhat.com> (raw)
In-Reply-To: <3748b6be-cd8b-19e6-eb36-c5f94850d764@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

On Thu, 2020-09-17 at 15:24 +0200, Hans de Goede wrote:
> > Excuse my ignorance, but why does "lap_mode" need to be here?
> > I understand the implications of it regarding performance, but
> > I think it would be more sense to export it via the hwmon (or
> > something similar) subsystem? What am I missing?
> 
> Well hwmon has very clearly defined sensor types, like voltage,
> fan-speed and temperature. lap_mode does not match any of them.

Not sure. I think you can consider it a simple sensor. In this case it
just affects thermal limits that are imposed on the system (and some
other stuff like RF for modems).

It does have a major impact on something like a "performance" mode
because of those imposed limits and causes these modes to be degraded.
But I think this interface can just show the configured state, even if
the component knows that the performance state is severely limited due
to other factors.

Benjamin

> Also registering another-type class device just for the lap_mode
> boolean seems overkill, esp. since lap_mode is inherently coupled
> to the performance-profile stuff.
> 
> Regards,
> 
> Hans
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2020-09-17 14:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 11:22 RFC: offering a standardized (/sys/class) userspace API for selecting system/laptop performance-profiles Hans de Goede
2020-09-17 11:50 ` Bastien Nocera
2020-09-17 12:51   ` Hans de Goede
2020-09-17 13:00     ` Bastien Nocera
2020-09-17 13:50     ` Benjamin Berg
2020-09-17 13:54       ` Hans de Goede
2020-09-17 14:10         ` Benjamin Berg
2020-09-17 16:58           ` [External] " Mark Pearson
2020-09-17 17:03             ` Hans de Goede
2020-09-17 17:16               ` Mark Pearson
2020-09-17 18:16                 ` Benjamin Berg
2020-09-21  9:03                   ` Elia Devito
2020-09-22 10:43                     ` Hans de Goede
2020-09-24  2:10                       ` Mark Pearson
2020-09-24  8:21                         ` Hans de Goede
2020-09-24 11:48                     ` Benjamin Berg
2020-09-22 10:30                 ` Hans de Goede
2020-09-24  1:44                   ` Mark Pearson
2020-09-17 13:36   ` Mark Pearson
2020-09-17 14:04     ` Hans de Goede
2020-09-17 16:51       ` Mark Pearson
2020-09-17 12:22 ` Benjamin Berg
2020-09-17 12:45   ` Hans de Goede
2020-09-17 13:07     ` Bastien Nocera
2020-09-17 13:46       ` Hans de Goede
2020-09-17 13:02 ` Barnabás Pőcze
2020-09-17 13:24   ` Hans de Goede
2020-09-17 13:28     ` Bastien Nocera
2020-09-17 13:51       ` Hans de Goede
2020-09-17 13:59     ` Benjamin Berg [this message]

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=0470605070bdce679e91aaa1523fe0cb94becc49.camel@redhat.com \
    --to=bberg@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=eliadevito@gmail.com \
    --cc=hadess@hadess.net \
    --cc=hdegoede@redhat.com \
    --cc=jaredz@redhat.com \
    --cc=mpearson@lenovo.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=pobrn@protonmail.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