[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08e3a1d264016aed93aca8632ee42637dc00d238.camel@hadess.net>
Date: Thu, 29 Oct 2020 13:33:28 +0100
From: Bastien Nocera <hadess@...ess.net>
To: Hans de Goede <hdegoede@...hat.com>,
Mark Pearson <markpearson@...ovo.com>
Cc: dvhart@...radead.org, mgross@...ux.intel.com,
mario.limonciello@...l.com, eliadevito@...il.com, bberg@...hat.com,
linux-pm@...r.kernel.org, linux-acpi@...r.kernel.org,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: Add documentation for new
platform_profile sysfs attribute
On Wed, 2020-10-28 at 18:23 +0100, Hans de Goede wrote:
>
> > It's not meaningless, but rather ambiguous. For a range of 1 to 5,
> > is 1
> > high performance, and 5 low power, or vice-versa?
>
> It is meaningless because the space we are trying to describe with
> the
> profile-names is not 1 dimensional. E.g. as discussed before cool and
> low-power are not necessarily the same thing. If you have a better
> way
> to word this I'm definitely in favor of improving the text here.
What do you think of:
> +Since numbers are a rather meaningless way to describe platform-
profiles
"Since numbers on their own cannot represent the multiple variables
that a profile will adjust (power consumption, heat generation, etc.)
..."
> +this API uses strings to describe the various profiles. To make sure that
> +userspace gets a consistent experience when using this API this API
> +document defines a fixed set of profile-names. Drivers *must* map their
> +internal profile representation/names onto this fixed set.
Powered by blists - more mailing lists