PM / devfreq: tegra30: Separate configurations per-SoC generation
authorDmitry Osipenko <digetx@gmail.com>
Thu, 3 Dec 2020 19:24:39 +0000 (22:24 +0300)
committerChanwoo Choi <cw00.choi@samsung.com>
Mon, 7 Dec 2020 01:25:51 +0000 (10:25 +0900)
commit6a575e84f11e15078629f0d16bff2bc354a6bfc0
treee592979fb488fd25abeab7ab03b7b08836bce198
parent16e8b2a7cb886bcc3dd89ad28948d374a2319bbc
PM / devfreq: tegra30: Separate configurations per-SoC generation

Previously we were using count-weight of the T124 for T30 in order to
get EMC clock rate that was reasonable for T30. In fact the count-weight
should be x2 times smaller on T30, but then devfreq was producing a bit
too low EMC clock rate for ISO memory clients, like display controller
for example.

Now both Tegra ACTMON and Tegra DRM display drivers support interconnect
framework and display driver tells to ICC what a minimum memory bandwidth
is needed, preventing FIFO underflows. Thus, now we can use a proper
count-weight value for Tegra30 and MC_ALL device config needs a bit more
aggressive boosting.

Add a separate ACTMON driver configuration that is specific to Tegra30.

Tested-by: Peter Geis <pgwipeout@gmail.com>
Tested-by: Nicolas Chauvet <kwizart@gmail.com>
Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
drivers/devfreq/tegra30-devfreq.c