Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
commit 73867c8709b569cdd7fda67f01dfe02c8d055521Author: Ankit Nautiyal <ankit.k.nautiyal@intel.com>Date: Tue Mar 15 13:32:46 2022 +0530 drm/i915/display: Remove check for low voltage sku for max dp source rate The low voltage sku check can be ignored as OEMs need to consider that when designing the board and then put any limits in VBT. Same is now changed in Bspec pages. Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5272 Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com> Reviewed-by: Imre Deak <imre.deak@intel.com> Signed-off-by: Imre Deak <imre.deak@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20220315080247.1161844-2-ankit.k.nautiyal@intel.com
Due to the regression #6205 (closed) I've pushed the revert d5929835080a ("drm/i915/display: Re-add check for low voltage sku for max dp source rate") to drm-intel-next.
The one thing I noticed in the log was some register mismatch in the combo PHY initialization. But it looks like neither the GOP or i915 program that exactly as the spec says (though the i915 value looks technically more in line with the spec).