CHROMIUM: drm/i915: Use max GFX freq on quad-core Baytrail
Set the idle freq and soft limit min freq to the max freq
at boot to prevent freq changes as a workaround for the
system hang on quad-core Baytrail devices.
BUG=chromium:719040
TEST=Verify no freq changes in valleyview_set_rps,
/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_cur_freq_mhz
shows the max freq. Run PLTs on Kip and Glimmer.
Original-Change-Id: I0371ed6681e8159d133bc6913341cf4a83bdc2f0
Signed-off-by: Ben Zhang <benzh@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/559856
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
(cherry picked from commit 2c7bc96919c88cb14245d1f2239394ff9abb135d)
Conflicts:
drivers/gpu/drm/i915/intel_pm.c
Manually applied the patch to R60 which doesn't have commit
773ea9a80132 ("drm/i915: Perform static RPS frequency setup
before userspace"). Although gen6_init_rps_frequencies also
writes idle_freq and the soft limits, it is not part of the
resume path intel_gen6_powersave_work on VLV. These rps freq
vars are written only one time during driver load on VLV in
valleyview_init_gt_powersave.
Verified on Kip the idle_freq and the soft limits are preserved
across suspend/resume.
Change-Id: Ie20ec3d54ed33bec0d804ca856914fe8b55ee4c1
Signed-off-by: Ben Zhang <benzh@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/567639
1 file changed
