summaryrefslogtreecommitdiff
path: root/oui-update.py
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2014-08-13 11:48:34 +0200
committerTobias Klauser <tklauser@distanz.ch>2014-08-13 11:48:34 +0200
commitfa32dcaddab2363cb01acc81bddf7dc3d42ab5b1 (patch)
tree821d03bd9d971849f84b3bddea9620b5167a6aba /oui-update.py
parent03e3d73dca588d2411bc1223c7cbd22ba2273b1e (diff)
netsniff 0.5.9-rc3v0.5.9-rc3
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'oui-update.py')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-12-14 11:44:35 +0000
>
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 'include/dt-bindings/power/r8a7790-sysc.h')