Re: [PATCH v1] cpufreq: tegra20: Use resource-managed API

2021-01-19 Thread Viresh Kumar
On 19-01-21, 18:01, Dmitry Osipenko wrote: > The regular devm_opp_* helpers won't be usable for CPUFreq drivers because > OPP is applied to the CPU device and not the device of the CPUFreq driver. Ahh, I missed that. > But maybe we could support such cases by the helpers? > > I CC'd Yangtao Li.

Re: [PATCH v1] cpufreq: tegra20: Use resource-managed API

2021-01-19 Thread Dmitry Osipenko
18.01.2021 09:39, Viresh Kumar пишет: > On 18-01-21, 02:18, Dmitry Osipenko wrote: >> Switch cpufreq-tegra20 driver to use resource-managed API. >> This removes the need to get opp_table pointer using >> dev_pm_opp_get_opp_table() in order to release OPP table that >> was requested by dev_pm_opp_se

Re: [PATCH v1] cpufreq: tegra20: Use resource-managed API

2021-01-17 Thread Viresh Kumar
On 18-01-21, 02:18, Dmitry Osipenko wrote: > Switch cpufreq-tegra20 driver to use resource-managed API. > This removes the need to get opp_table pointer using > dev_pm_opp_get_opp_table() in order to release OPP table that > was requested by dev_pm_opp_set_supported_hw(), making the code > a bit mo

[PATCH v1] cpufreq: tegra20: Use resource-managed API

2021-01-17 Thread Dmitry Osipenko
Switch cpufreq-tegra20 driver to use resource-managed API. This removes the need to get opp_table pointer using dev_pm_opp_get_opp_table() in order to release OPP table that was requested by dev_pm_opp_set_supported_hw(), making the code a bit more straightforward. Signed-off-by: Dmitry Osipenko