config VHOST_NET tristate "Host kernel accelerator for virtio net" depends on NET && EVENTFD && (TUN || !TUN) && (MACVTAP || !MACVTAP) select VHOST ---help--- This kernel module can be loaded in host kernel to accelerate guest networking with virtio_net. Not to be confused with virtio_net module itself which needs to be loaded in guest kernel. To compile this driver as a module, choose M here: the module will be called vhost_net. config VHOST_SCSI tristate "VHOST_SCSI TCM fabric driver" depends on TARGET_CORE && EVENTFD && m select VHOST default n ---help--- Say M here to enable the vhost_scsi TCM fabric module for use with virtio-scsi guests config VHOST_VSOCK tristate "vhost virtio-vsock driver" depends on VSOCKETS && EVENTFD select VIRTIO_VSOCKETS_COMMON select VHOST default n ---help--- This kernel module can be loaded in the host kernel to provide AF_VSOCK sockets for communicating with guests. The guests must have the virtio_transport.ko driver loaded to use the virtio-vsock device. To compile this driver as a module, choose M here: the module will be called vhost_vsock. config VHOST tristate ---help--- This option is selected by any driver which needs to access the core of vhost. config VHOST_CROSS_ENDIAN_LEGACY bool "Cross-endian support for vhost" default n ---help--- This option allows vhost to support guests with a different byte ordering from host while using legacy virtio. Userspace programs can control the feature using the VHOST_SET_VRING_ENDIAN and VHOST_GET_VRING_ENDIAN ioctls. This is only useful on a few platforms (ppc64 and arm64). Since it adds some overhead, it is disabled by default. If unsure, say "N". 3ce2d0'>refslogtreecommitdiff
path: root/sound/soc/codecs/wm8904.c
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-12 17:15:56 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-30 10:17:32 +0100
commite6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0 (patch)
tree77cadb6d8aad1b52c34e4afa8c9deef603bbe2ed /sound/soc/codecs/wm8904.c
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/soc/codecs/wm8904.c')