Re: [PATCH] drm/panfrost: make devfreq optional again

2019-06-05 Thread Neil Armstrong
On 03/06/2019 21:54, Ezequiel Garcia wrote: > On Fri, 2019-05-31 at 14:37 +0200, Neil Armstrong wrote: >> Devfreq runtime usage was made mandatory, thus making panfrost fail to probe >> on Amlogic S912 SoCs missin the "operating-points-v2" property. >> Make it optional again, leaving PM_DEVFREQ is

Re: [PATCH] drm/panfrost: make devfreq optional again

2019-06-03 Thread Ezequiel Garcia
On Fri, 2019-05-31 at 14:37 +0200, Neil Armstrong wrote: > Devfreq runtime usage was made mandatory, thus making panfrost fail to probe > on Amlogic S912 SoCs missin the "operating-points-v2" property. > Make it optional again, leaving PM_DEVFREQ is selected by default. > > Fixes: f3617b449d

Re: [PATCH] drm/panfrost: make devfreq optional again

2019-05-31 Thread Ezequiel Garcia
On Fri, 2019-05-31 at 14:37 +0200, Neil Armstrong wrote: > Devfreq runtime usage was made mandatory, thus making panfrost fail to probe > on Amlogic S912 SoCs missin the "operating-points-v2" property. > Make it optional again, leaving PM_DEVFREQ is selected by default. > > Fixes: f3617b449d

[PATCH] drm/panfrost: make devfreq optional again

2019-05-31 Thread Neil Armstrong
Devfreq runtime usage was made mandatory, thus making panfrost fail to probe on Amlogic S912 SoCs missin the "operating-points-v2" property. Make it optional again, leaving PM_DEVFREQ is selected by default. Fixes: f3617b449d ("drm/panfrost: Select devfreq") Signed-off-by: Neil Armstrong ---