[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Feb 2023 01:41:10 -0600
From: Russell Haley <yumpusamongus@...il.com>
To: Wyes Karny <wyes.karny@....com>,
Rafael J Wysocki <rafael@...nel.org>,
Huang Rui <ray.huang@....com>,
Jonathan Corbet <corbet@....net>,
Viresh Kumar <viresh.kumar@...aro.org>,
Mario.Limonciello@....com, Perry.Yuan@....com
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, Bagas Sanjaya <bagasdotme@...il.com>,
santosh.shukla@....com, Len Brown <lenb@...nel.org>,
Robert Moore <robert.moore@...el.com>,
Borislav Petkov <bp@...en8.de>,
Ananth Narayan <ananth.narayan@....com>,
gautham.shenoy@....com, Tor Vic <torvic9@...lbox.org>
Subject: Re: [PATCH v4 5/6] cpufreq: amd_pstate: Add guided mode control
support via sysfs
On 1/30/23 23:21, Wyes Karny wrote:
> Only if the state requested matches
> with the current state then -EBUSY value is returned.
This differs from the behavior of intel_pstate, where writing the
current state to the status file always succeeds.
Why not do the same thing here?
Powered by blists - more mailing lists