00ecf'/>
summaryrefslogtreecommitdiff
path: root/drivers/usb/serial/ch341.c
it.cgi/linux/net-next.git/diff/include/uapi/drm/radeon_drm.h?id=0d2164af2696821b27b04bebd8420b0e881bf44d&id2=f181d6a3bcc35633facf5f3925699021c13492c5'>radeon_drm.h
diff options
AgeCommit message (Expand)AuthorFilesLines
context:
space:
mode:
Diffstat (limited to 'include/uapi/drm/radeon_drm.h')
-next.git/tree/sound/pci/ctxfi/ctimap.h?id=e6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0'>sound/pci/ctxfi/ctimap.h
parent4e5b54f127426c82dc2816340c26d951a5bb3429 (diff)
drm: Don't race connector registration
I was under the misconception that the sysfs dev stuff can be fully set up, and then registered all in one step with device_add. That's true for properties and property groups, but not for parents and child devices. Those must be fully registered before you can register a child. Add a bit of tracking to make sure that asynchronous mst connector hotplugging gets this right. For consistency we rely upon the implicit barriers of the connector->mutex, which is taken anyway, to ensure that at least either the connector or device registration call will work out. Mildly tested since I can't reliably reproduce this on my mst box here. Reported-by: Dave Hansen <dave.hansen@intel.com> Cc: Dave Hansen <dave.hansen@intel.com> Acked-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/1484237756-2720-1-git-send-email-daniel.vetter@ffwll.ch
Diffstat (limited to 'sound/pci/ctxfi/ctimap.h')