== Series Details ==
Series: drm/i915: Fix incorrect virtual PCH_NONE/PCH_NOP assignment
URL : https://patchwork.freedesktop.org/series/43833/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4247_full -> Patchwork_9133_full =
== Summary - WARNING ==
Minor unknown changes c
== Series Details ==
Series: drm/i915: Fix incorrect virtual PCH_NONE/PCH_NOP assignment
URL : https://patchwork.freedesktop.org/series/43833/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4247 -> Patchwork_9133 =
== Summary - SUCCESS ==
No regressions found.
External
From: Colin Xu
On BXT platform, guest kernel request PCH_NONE to initialize display
correctly.
Signed-off-by: Colin Xu
---
drivers/gpu/drm/i915/i915_drv.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index 637ba86104b
From: Colin Xu
In recent virtual PCH detection refactoring patch, virtual pch id
is guessed and sanity checked from dev_priv. However, on platform that
has no PCH like BXT, the guessing is wrong by mixing up PCH_NONE with
PCH_NOP.
The patch set handles such situation so that correct virtual PCH_N
From: Colin Xu
The existing way to update virtual PCH will return wrong PCH type
in case the host doesn't have PCH:
- intel_virt_detect_pch returns guessed PCH id 0
- id 0 maps to PCH_NOP. >> should be PCH_NONE.
Since PCH_NONE and PCH_NOP are different types, mixing them up
will break vbt ini
Hi Mika,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20180517]
[cannot apply to drm-intel/for-linux-next v4.17-rc6 v4.17-rc5 v4.17-rc4
v4.17-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
ht
