mirror of
https://github.com/torvalds/linux.git
synced 2024-12-03 09:31:26 +00:00
03a9606e7f
drm_fb_helper_is_bound() is used to check if DRM userspace is in control. This is done by looking at the fb on the primary plane. By the time fb-helper gets around to committing, it's possible that the facts have changed. Avoid this race by holding the drm_device->master_mutex lock while committing. When DRM userspace does its first open, it will now wait until fb-helper is done. The helper will stay away if there's a master. Two igt tests fail with the new 'bail out if master' rule. Work around this by relaxing this rule for drm_fb_helper_restore_fbdev_mode_unlocked() until the tests have been fixed. Add todo entry for this. Locking rule: Always take the fb-helper lock first. v5: drm_fb_helper_restore_fbdev_mode_unlocked(): Use restore_fbdev_mode_force() v2: - Remove drm_fb_helper_is_bound() (Daniel Vetter) - No need to check fb_helper->dev->master in drm_fb_helper_single_fb_probe(), restore_fbdev_mode() has the check. Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Noralf Trønnes <noralf@tronnes.org> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: https://patchwork.freedesktop.org/patch/msgid/20190506180139.6913-3-noralf@tronnes.org |
||
---|---|---|
.. | ||
bridge | ||
dp-mst | ||
afbc.rst | ||
amdgpu-dc.rst | ||
amdgpu.rst | ||
conf.py | ||
drivers.rst | ||
drm-client.rst | ||
drm-internals.rst | ||
drm-kms-helpers.rst | ||
drm-kms.rst | ||
drm-mm.rst | ||
drm-uapi.rst | ||
i915.rst | ||
index.rst | ||
introduction.rst | ||
kms-properties.csv | ||
komeda-kms.rst | ||
meson.rst | ||
msm-crash-dump.rst | ||
pl111.rst | ||
tegra.rst | ||
tinydrm.rst | ||
todo.rst | ||
tve200.rst | ||
v3d.rst | ||
vc4.rst | ||
vga-switcheroo.rst | ||
vgaarbiter.rst | ||
vkms.rst | ||
xen-front.rst |