Home
last modified time | relevance | path

Searched refs:unplug (Results 1 – 25 of 35) sorted by relevance

12

/linux/drivers/gpu/drm/panthor/
H A Dpanthor_device.c75 mutex_lock(&ptdev->unplug.lock); in panthor_device_unplug()
80 mutex_unlock(&ptdev->unplug.lock); in panthor_device_unplug()
81 wait_for_completion(&ptdev->unplug.done); in panthor_device_unplug()
93 mutex_unlock(&ptdev->unplug.lock); in panthor_device_unplug()
115 complete_all(&ptdev->unplug.done); in panthor_device_unplug()
181 init_completion(&ptdev->unplug.done); in panthor_device_init()
182 ret = drmm_mutex_init(&ptdev->base, &ptdev->unplug.lock); in panthor_device_init()
H A Dpanthor_device.h148 } unplug; member
/linux/drivers/md/
H A Draid1-10.c134 blk_plug_cb_fn unplug, int copies) in raid1_add_bio_to_plug() argument
148 cb = blk_check_plugged(unplug, mddev, sizeof(*plug)); in raid1_add_bio_to_plug()
171 mddev->bitmap_ops->unplug(mddev, current->bio_list == NULL); in raid1_prepare_flush_writes()
/linux/Documentation/arch/s390/
H A Dvfio-ap-locking.rst72 device driver is using it to plug/unplug AP devices passed through to the KVM
86 to unplug the adapter.
89 pointer is not used to plug/unplug devices passed through to the KVM guest;
H A Dvfio-ap.rst970 Hot plug/unplug support:
1026 | dyn | Indicates hot plug/unplug of AP adapters, domains and control |
1041 1. If the KVM guest was started with libvirt, you can hot unplug the mdev via
1046 For example, to hot unplug mdev 62177883-f1bb-47f0-914d-32a22e3a8804 from
1064 For example, to hot unplug the vfio_ap mediated device identified on the
1076 For example, to hot unplug the vfio_ap mediated device that was specified
/linux/drivers/gpu/drm/ci/xfails/
H A Di915-glk-flakes.txt6 core_hotunplug@unplug-rescan
/linux/include/uapi/linux/
H A Dvirtio_mem.h82 * has memory plugged. The device driver can request to unplug all memory
101 /* request to unplug memory blocks */
103 /* request to unplug all blocks and shrink the usable size */
132 struct virtio_mem_req_unplug unplug;
208 * Currently used size. Changes due to plug/unplug requests, but no
130 struct virtio_mem_req_unplug unplug; global() member
/linux/arch/x86/xen/
H A DMakefile23 obj-$(CONFIG_XEN_PVHVM) += platform-pci-unplug.o
/linux/Documentation/usb/
H A Dchipidea.rst66 5) Remove B-device (unplug micro B plug) and insert again in 10 seconds;
69 6) Remove B-device (unplug micro B plug) and insert again after 10 seconds;
/linux/drivers/thunderbolt/
H A Dtb.c82 bool unplug; member
93 static void tb_queue_hotplug(struct tb *tb, u64 route, u8 port, bool unplug) in tb_queue_hotplug() argument
104 ev->unplug = unplug; in tb_queue_hotplug()
2409 ev->route, ev->port, ev->unplug); in tb_handle_hotplug()
2415 ev->route, ev->port, ev->unplug); in tb_handle_hotplug()
2421 ev->route, ev->port, ev->unplug); in tb_handle_hotplug()
2427 if (ev->unplug) { in tb_handle_hotplug()
2889 if (tb_cfg_ack_plug(tb->ctl, route, pkg->port, pkg->unplug)) { in tb_handle_event()
2894 tb_queue_hotplug(tb, route, pkg->port, pkg->unplug); in tb_handle_event()
H A Dctl.h127 int tb_cfg_ack_plug(struct tb_ctl *ctl, u64 route, u32 port, bool unplug);
H A Dctl.c819 * tb_cfg_ack_plug() - Ack hot plug/unplug event
822 * @port: Port where the hot plug/unplug happened
823 * @unplug: Ack hot plug or unplug
825 * Call this as response for hot plug/unplug event to ack it. in tb_cfg_ack_plug() argument
828 int tb_cfg_ack_plug(struct tb_ctl *ctl, u64 route, u32 port, bool unplug) in tb_cfg_ack_plug()
834 .pg = unplug ? TB_CFG_ERROR_PG_HOT_UNPLUG in tb_cfg_ack_plug()
838 unplug ? "un" : "", route, port);
/linux/Documentation/userspace-api/media/mediactl/
H A Dmedia-ioc-device-info.rst99 vary across reboots or device unplug/replug.
/linux/Documentation/networking/device_drivers/atm/
H A Dcxacru.rst11 driver and it is necessary to unplug/remove power to the device to fix this.
/linux/drivers/hid/bpf/progs/
H A DREADME77 Then unplug and replug the device.
/linux/Documentation/sound/designs/
H A Djack-injection.rst15 machine and plug/unplug physical devices to the audio jack.
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-vfio-mdev110 is active and the vendor driver doesn't support hot unplug.
/linux/kernel/
H A DKconfig.kexec127 in response to hot plug/unplug or online/offline of CPUs or
/linux/Documentation/driver-api/tty/
H A Dmoxa-smartio.rst196 To avoid this problem, please unplug fifth and after board, because Moxa
/linux/Documentation/gpu/
H A Dvkms.rst147 - Change output configuration: Plug/unplug screens, change EDID, allow changing
/linux/Documentation/driver-api/
H A Dvfio-mediated-device.rst237 doesn't support hot unplug.
/linux/Documentation/driver-api/cxl/
H A Dmemory-devices.rst195 objects. Conversely for hot-unplug / removal scenarios, there is no need for
/linux/Documentation/driver-api/usb/
H A Dpersist.rst124 with it, unplug the flash device, plug it back in later, and still
/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
H A Doverview.rst119 the ability to hot plug/unplug objects in and out of the DPRC.
/linux/drivers/virtio/
H A Dvirtio_mem.c31 MODULE_PARM_DESC(unplug_online, "Try to unplug online memory");
105 /* We might first have to unplug all memory when starting up. */
108 /* Workqueue that processes the plug/unplug requests. */
250 /* Timer for retrying to plug/unplug memory. */
711 * We might have freed up memory we can now unplug, retry in virtio_mem_remove_memory()
754 * We might have freed up memory we can now unplug, retry in virtio_mem_offline_and_remove_memory()
1068 * maybe we can handle pending unplug requests. in virtio_mem_memory_notifier_cb()
1463 .u.unplug.addr = cpu_to_virtio64(vm->vdev, addr), in virtio_mem_send_unplug_request()
1464 .u.unplug.nb_blocks = cpu_to_virtio16(vm->vdev, nb_vm_blocks), in virtio_mem_send_unplug_request()
1556 * Request to unplug
[all...]

12