[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6f0693f9-3efe-d1f0-18b1-90dda7b3d0a4@arm.com>
Date: Mon, 2 Mar 2020 14:58:33 +0000
From: Steven Price <steven.price@....com>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: tomeu.vizoso@...labora.com, airlied@...ux.ie,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-rockchip@...ts.infradead.org, sudeep.holla@....com,
linux-amlogic@...ts.infradead.org, robin.murphy@....com,
alyssa@...enzweig.io
Subject: Re: [PATCH RFT v2 0/3] devfreq fixes for panfrost
On 22/02/2020 19:42, Martin Blumenstingl wrote:
> Hi Steven,
>
> On Sun, Jan 12, 2020 at 1:16 AM Martin Blumenstingl
> <martin.blumenstingl@...glemail.com> wrote:
>>
[...]
>>
>>
>> Martin Blumenstingl (3):
>> drm/panfrost: enable devfreq based the "operating-points-v2" property
>> drm/panfrost: call dev_pm_opp_of_remove_table() in all error-paths
>> drm/panfrost: Use the mali-supply regulator for control again
> I don't have time to work on these patches in the near future
> can you (or if someone else is interested then please speak up) please
> take these over? you are familiar with the panfrost devfreq code and
> you have at least one board where the GPU regulator actually has to
> change the voltage (which means you can test this properly; on Amlogic
> SoCs the GPU voltage is fixed across all frequencies).
Hi Martin,
Sorry for the slow response - yes I can pick this up. Although I've got
some other things to catch up with first.
Thanks,
Steve
Powered by blists - more mailing lists