diff options
| author | Daniel Vetter | 2015-07-09 23:44:26 +0200 |
|---|---|---|
| committer | Daniel Vetter | 2015-07-22 16:25:45 +0200 |
| commit | 8c4ccc4ab6f64e859d4ff8d7c02c2ed2e956e07f (patch) | |
| tree | c982a3c30b849e7ebea40fe2eed4c6757ad63a0a /drivers/gpu/drm/drm_fb_helper.c | |
| parent | drm: Add modeset object iterators (diff) | |
| download | kernel-qcow2-linux-8c4ccc4ab6f64e859d4ff8d7c02c2ed2e956e07f.tar.gz kernel-qcow2-linux-8c4ccc4ab6f64e859d4ff8d7c02c2ed2e956e07f.tar.xz kernel-qcow2-linux-8c4ccc4ab6f64e859d4ff8d7c02c2ed2e956e07f.zip | |
drm/probe-helper: Grab mode_config.mutex in poll_init/enable
So on first looks this seems superflous since drivers should ensure
correct ordering to not make this a problem. Otoh ordering constraints
between hdp, fbdev load and enabling polling are already tricky on
some hardware and it helps to be more robust.
But the real goal is to just shut up a locking WARN_ON I'd like to
add, which means init code gets some additional locks just for
uniformity.
v2: Also grab the lock for the public poll_enable, not just poll_init
which is used for resume, with the same justification.
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Diffstat (limited to 'drivers/gpu/drm/drm_fb_helper.c')
0 files changed, 0 insertions, 0 deletions