The TGL+ bw code has an off by one error on the num_planes
calculation, and tgl_max_bw_index() incorrectly bumps
the num_planes to 1 from 0.
That approach made sense on ICL where num_planes is more or
less a minimum number of planes to consider for the group,
but on TGL+ num_planes really is a maximum number of planes,
so these adjustments no longer make any sense there.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patch.msgid.link/20260522200346.17377-2-ville.syrjala@linux.intel.com
Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>
bi_next = &display->bw.max[i + 1];
if (clpchgroup < clperchgroup)
- bi_next->num_planes = (ipqdepth - clpchgroup) /
- clpchgroup + 1;
+ bi_next->num_planes = (ipqdepth - clpchgroup) / clpchgroup;
else
bi_next->num_planes = 0;
}
{
int i;
- /*
- * Let's return max bw for 0 planes
- */
- num_planes = max(1, num_planes);
-
for (i = ARRAY_SIZE(display->bw.max) - 1; i >= 0; i--) {
const struct intel_bw_info *bi =
&display->bw.max[i];