18c2ecf20Sopenharmony_ciWhat: /sys/bus/vmbus/devices/.../driver_override 28c2ecf20Sopenharmony_ciDate: August 2019 38c2ecf20Sopenharmony_ciContact: Stephen Hemminger <sthemmin@microsoft.com> 48c2ecf20Sopenharmony_ciDescription: 58c2ecf20Sopenharmony_ci This file allows the driver for a device to be specified which 68c2ecf20Sopenharmony_ci will override standard static and dynamic ID matching. When 78c2ecf20Sopenharmony_ci specified, only a driver with a name matching the value written 88c2ecf20Sopenharmony_ci to driver_override will have an opportunity to bind to the 98c2ecf20Sopenharmony_ci device. The override is specified by writing a string to the 108c2ecf20Sopenharmony_ci driver_override file (echo uio_hv_generic > driver_override) and 118c2ecf20Sopenharmony_ci may be cleared with an empty string (echo > driver_override). 128c2ecf20Sopenharmony_ci This returns the device to standard matching rules binding. 138c2ecf20Sopenharmony_ci Writing to driver_override does not automatically unbind the 148c2ecf20Sopenharmony_ci device from its current driver or make any attempt to 158c2ecf20Sopenharmony_ci automatically load the specified driver. If no driver with a 168c2ecf20Sopenharmony_ci matching name is currently loaded in the kernel, the device 178c2ecf20Sopenharmony_ci will not bind to any driver. This also allows devices to 188c2ecf20Sopenharmony_ci opt-out of driver binding using a driver_override name such as 198c2ecf20Sopenharmony_ci "none". Only a single driver may be specified in the override, 208c2ecf20Sopenharmony_ci there is no support for parsing delimiters. 218c2ecf20Sopenharmony_ci 22