summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2026-07-15 15:09:26 +0300
committerVille Syrjälä <ville.syrjala@linux.intel.com>2026-07-17 18:01:26 +0300
commitf69946f6d891aca1614233573741543b3bab4e6a (patch)
treecb6eaa784972360d95baf27e307cc846cd8b5a80 /include
parent776308ab96b29cf4fac71dfcdc91228811031bfe (diff)
downloadlinux-next-f69946f6d891aca1614233573741543b3bab4e6a.tar.gz
linux-next-f69946f6d891aca1614233573741543b3bab4e6a.zip
drm/i915/cdclk: Deal with 2 PPC hscale issues when calculating min CDCLK
Double the fractional part of the horizontal scale factor for the purposes of min_cdck calculation. This bumps the min CDCLK sufficiently to overcome some kind of 2 PPC granularity issue. Without this CDCLK may end up being too low and we get underruns with certain horizontal downscale factors. The current Bspec formula calls for doubling only the fractional part below 0.5, and rounding it down to a unit fraction. But that formula does not result in a sufficient CDCLK bump in a lot of cases. Empirical evidence supports doubling the entire fractional part, so let's just do that while we wait for further analysis from the hardware team. Also note that the position of the scaler output window also seems to matter. If the output is near the left edge of the screen then lower CDCLK is sufficient, but moving the output window further to the right causes underruns unless CDCLK is also bumped. Some prefill happening during hblank already? Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patch.msgid.link/20260715120926.10786-5-ville.syrjala@linux.intel.com Reviewed-by: Nemesa Garg <nemesa.garg@intel.com> Tested-by: Vidya Srinivas <vidya.srinivas@intel.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions