On 5/15/20 7:09 PM, Valentin Schneider wrote:
On 15/05/20 01:48, Francisco Jerez wrote:
Valentin Schneider writes:
(+Lukasz)
On 11/05/20 22:01, Francisco Jerez wrote:
What I'm missing is an explanation for why this isn't using the
infrastructure that was build for these kinds of
On 15/05/20 01:48, Francisco Jerez wrote:
> Valentin Schneider writes:
>
>> (+Lukasz)
>>
>> On 11/05/20 22:01, Francisco Jerez wrote:
What I'm missing is an explanation for why this isn't using the
infrastructure that was build for these kinds of things? The thermal
framework,
Valentin Schneider writes:
> (+Lukasz)
>
> On 11/05/20 22:01, Francisco Jerez wrote:
>>> What I'm missing is an explanation for why this isn't using the
>>> infrastructure that was build for these kinds of things? The thermal
>>> framework, was AFAIU, supposed to help with these things, and the
"Rafael J. Wysocki" writes:
> On Monday, May 11, 2020 11:01:41 PM CEST Francisco Jerez wrote:
>>
>> --==-=-=
>> Content-Type: multipart/mixed; boundary="=-=-="
>>
>> --=-=-=
>> Content-Type: text/plain; charset=utf-8
>> Content-Disposition: inline
>> Content-Transfer-Encoding: quoted-printable
(+Lukasz)
On 11/05/20 22:01, Francisco Jerez wrote:
>> What I'm missing is an explanation for why this isn't using the
>> infrastructure that was build for these kinds of things? The thermal
>> framework, was AFAIU, supposed to help with these things, and the IPA
>> thing in particular is used
On Monday, May 11, 2020 11:01:41 PM CEST Francisco Jerez wrote:
>
> --==-=-=
> Content-Type: multipart/mixed; boundary="=-=-="
>
> --=-=-=
> Content-Type: text/plain; charset=utf-8
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Peter Zijlstra writes:
>
> > On
Peter Zijlstra writes:
> On Mon, Apr 27, 2020 at 08:22:47PM -0700, Francisco Jerez wrote:
>> This addresses the technical concerns people brought up about my
>> previous v2 revision of this series. Other than a few bug fixes, the
>> only major change relative to v2 is that the controller is now
On Mon, Apr 27, 2020 at 08:22:47PM -0700, Francisco Jerez wrote:
> This addresses the technical concerns people brought up about my
> previous v2 revision of this series. Other than a few bug fixes, the
> only major change relative to v2 is that the controller is now exposed
> as a new CPUFREQ
This addresses the technical concerns people brought up about my
previous v2 revision of this series. Other than a few bug fixes, the
only major change relative to v2 is that the controller is now exposed
as a new CPUFREQ generic governor as requested by Rafael (named
"adaptive" in this RFC
