| commit | de0a3d094de0858f091cf353c437e912ca41a506 | |
| author | Sharat Masetty <smasetty@codeaurora.org> | |
| Thu, 4 Oct 2018 09:41:42 +0000 (4 15:11 +0530) | ||
| committer | Rob Clark <robdclark@gmail.com> | |
| Thu, 4 Oct 2018 13:14:20 +0000 (4 09:14 -0400) | ||
| tree | 90ee21de75988516758d4d3b0be388833dc90df9 | treesnapshot (tar.gz zip) |
| parent | c28aa2031f64701d4a1a78f97147e93fc5eb0c04 | commitdiff |
drm/msm: re-factor devfreq code
The devfreq framework requires the drivers to provide busy time estimations.
The GPU driver relies on the hardware performance counteres for the busy time
estimations, but different hardware revisions have counters which can be
sourced from different clocks. So the busy time estimation will be target
dependent. Additionally on targets where the clocks are completely controlled
by the on chip microcontroller, fetching and setting the current GPU frequency
will be different. This patch aims to embrace these differences by re-factoring
the devfreq code a bit.
Signed-off-by: Sharat Masetty <smasetty@codeaurora.org>
Signed-off-by: Rob Clark <robdclark@gmail.com>
The devfreq framework requires the drivers to provide busy time estimations.
The GPU driver relies on the hardware performance counteres for the busy time
estimations, but different hardware revisions have counters which can be
sourced from different clocks. So the busy time estimation will be target
dependent. Additionally on targets where the clocks are completely controlled
by the on chip microcontroller, fetching and setting the current GPU frequency
will be different. This patch aims to embrace these differences by re-factoring
the devfreq code a bit.
Signed-off-by: Sharat Masetty <smasetty@codeaurora.org>
Signed-off-by: Rob Clark <robdclark@gmail.com>
| drivers/gpu/drm/msm/adreno/a5xx_gpu.c | diffblobblamehistory | |
| drivers/gpu/drm/msm/msm_gpu.c | diffblobblamehistory | |
| drivers/gpu/drm/msm/msm_gpu.h | diffblobblamehistory |