summaryrefslogtreecommitdiffstats
path: root/drivers/mfd
diff options
context:
space:
mode:
authorXiong Zhang <xiong.y.zhang@intel.com>2018-03-28 05:30:14 +0800
committerZhenyu Wang <zhenyuw@linux.intel.com>2018-03-30 14:47:19 +0800
commit65eff272330c72689fb5e20dd6491826fd87a39c (patch)
tree5acb307dbec3341f92ead6c8f6cb784f5ceb8c15 /drivers/mfd
parenta733390f9a79876635013e57da25f91b6e78ffe6 (diff)
downloadlinux-stable-65eff272330c72689fb5e20dd6491826fd87a39c.tar.gz
linux-stable-65eff272330c72689fb5e20dd6491826fd87a39c.tar.bz2
linux-stable-65eff272330c72689fb5e20dd6491826fd87a39c.zip
drm/i915/gvt: Disable primary/sprite/cursor plane at virtual display initialization
Much error exist in host dmesg during guest boot up with loca display enabled. gvt: vgpu 1: invalid range gmadr 0x0 size 0x0 This error happens when qemu get dmabuf info in case that the virtual display plane is enabled but its base address is an invalid 0, such case may be true before guest enable its plane. At this moment, its state is copied from host where the plane may be enabled. This patch disable primary/sprite/cursor plane at virtual display initialization, so intel_vgpu_decode_primary/cursor/sprite could return early as plane is disabled, then plane base check is skipped and error message disapper. Signed-off-by: Xiong Zhang <xiong.y.zhang@intel.com> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Diffstat (limited to 'drivers/mfd')
0 files changed, 0 insertions, 0 deletions