| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-amba | 1 What: /sys/bus/amba/devices/.../driver_override
8 written to driver_override will have an opportunity to bind to
10 driver_override file (echo vfio-amba > driver_override) and may
11 be cleared with an empty string (echo > driver_override).
13 Writing to driver_override does not automatically unbind the
18 driver binding using a driver_override name such as "none".
|
| H A D | sysfs-bus-vmbus | 1 What: /sys/bus/vmbus/devices/.../driver_override
8 to driver_override will have an opportunity to bind to the
10 driver_override file (echo uio_hv_generic > driver_override) and
11 may be cleared with an empty string (echo > driver_override).
13 Writing to driver_override does not automatically unbind the
18 opt-out of driver binding using a driver_override name such as
|
| H A D | sysfs-bus-vdpa | 39 What: /sys/bus/vdpa/devices/.../driver_override
45 written to driver_override will have an opportunity to bind to
47 driver_override file (echo vhost-vdpa > driver_override) and may
48 be cleared with an empty string (echo > driver_override).
50 Writing to driver_override does not automatically unbind the
55 driver binding using a driver_override name such as "none".
|
| H A D | sysfs-bus-platform | 1 What: /sys/bus/platform/devices/.../driver_override
8 written to driver_override will have an opportunity to bind
10 to the driver_override file (echo vfio-platform > \
11 driver_override) and may be cleared with an empty string
12 (echo > driver_override). This returns the device to standard
13 matching rules binding. Writing to driver_override does not
18 devices to opt-out of driver binding using a driver_override
|
| H A D | sysfs-bus-css | 35 What: /sys/bus/css/devices/.../driver_override
40 to driver_override will have an opportunity to bind to the
42 driver_override file (echo vfio-ccw > driver_override) and
43 may be cleared with an empty string (echo > driver_override).
45 Writing to driver_override does not automatically unbind the
50 opt-out of driver binding using a driver_override name such as
|
| H A D | sysfs-bus-wmi | 1 What: /sys/bus/wmi/devices/.../driver_override
8 written to driver_override will have an opportunity to bind
11 driver_override file (echo wmi-event-dummy > driver_override).
13 driver_override) which returns the device to standard matching
15 Writing to driver_override does not automatically unbind the
21 driver_override name such as "none". Only a single driver may be
|
| H A D | sysfs-bus-rpmsg | 77 What: /sys/bus/rpmsg/devices/.../driver_override
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | binding.rst | 108 a device's ``driver_override`` sysfs attribute. When set, only a driver
113 the device to standard matching rules. Writing to ``driver_override``
117 Buses opt into this mechanism by setting the ``driver_override`` flag in
122 .driver_override = true,
126 ``driver_override`` sysfs attribute for every device on that bus.
|
| /linux/include/linux/cdx/ |
| H A D | cdx_bus.h | 80 #define CDX_DEVICE_DRIVER_OVERRIDE(vend, dev, driver_override) \ argument
82 .subdevice = CDX_ANY_ID, .override_only = (driver_override)
|
| /linux/include/linux/ |
| H A D | rpmsg.h | 170 const char *driver_override);
197 const char *driver_override) in rpmsg_register_device_override() argument
|
| H A D | device.h | 722 } driver_override; member
891 guard(spinlock)(&dev->driver_override.lock); in device_has_driver_override()
892 return !!dev->driver_override.name; in device_has_driver_override()
907 guard(spinlock)(&dev->driver_override.lock); in device_match_driver_override()
908 if (dev->driver_override.name) in device_match_driver_override()
909 return !strcmp(dev->driver_override.name, drv->name); in device_match_driver_override()
|
| H A D | pci.h | 1075 #define PCI_DEVICE_DRIVER_OVERRIDE(vend, dev, driver_override) \ argument
1077 .subdevice = PCI_ANY_ID, .override_only = (driver_override)
|
| /linux/tools/testing/selftests/vfio/scripts/ |
| H A D | cleanup.sh | 16 if [ -f ${device_dir}/driver_override ]; then
|
| H A D | setup.sh | 41 touch ${device_dir}/driver_override
|
| H A D | lib.sh | 37 write_to /sys/bus/pci/devices/${1}/driver_override ${2}
|
| /linux/Documentation/admin-guide/gpio/ |
| H A D | gpio-aggregator.rst | 188 gpio-aggregator driver, or by writing to the "driver_override" file in Sysfs.
204 2. Binding manually using "driver_override":
208 $ echo gpio-aggregator > /sys/bus/platform/devices/door/driver_override
|
| /linux/Documentation/networking/device_drivers/ethernet/amd/ |
| H A D | pds_vfio_pci.rst | 45 echo "pds-vfio-pci" > /sys/class/pci_bus/$PF_BUS/device/$VF_BDF/driver_override
|
| /linux/drivers/nvdimm/ |
| H A D | Kconfig | 115 devices using 'driver_override' device attribute.
|
| /linux/Documentation/spi/ |
| H A D | spidev.rst | 66 echo spidev > /sys/bus/spi/devices/spiB.C/driver_override
|
| /linux/drivers/spi/ |
| H A D | spi.c | 90 guard(spinlock)(&dev->driver_override.lock); in driver_override_show()
91 return sysfs_emit(buf, "%s\n", dev->driver_override.name ?: ""); in driver_override_show()
93 static DEVICE_ATTR_RW(driver_override);
|
| /linux/drivers/vdpa/ |
| H A D | vdpa.c | 82 .driver_override = true,
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-port.rst | 257 $ echo mlx5_vfio_pci > /sys/bus/pci/devices/0000:08:00.0/driver_override
|