Searched full:driver (Results 1 – 25 of 2430) sorted by relevance
12345678910>>...98
| /Documentation/networking/ |
| D | mac80211-auth-assoc-deauth.txt | 11 participant driver
17 mac80211->driver: sta_state(AP, not-exists)
18 mac80211->driver: bss_info_changed(clear BSSID)
20 note over mac80211,driver
26 mac80211->driver: config(channel, channel type)
27 mac80211->driver: bss_info_changed(set BSSID, basic rate bitmap)
28 mac80211->driver: sta_state(AP, exists)
31 mac80211->driver: TX directed probe request
32 driver->mac80211: RX probe response
35 mac80211->driver: TX auth frame
[all …]
|
| /Documentation/driver-api/ |
| D | console.rst | 9 This type will be called 'system driver', and only one system driver is allowed
10 to exist. The system driver is persistent and it can never be unloaded, though
14 'modular driver' by this document. Multiple modular drivers can coexist at
15 any time with each driver sharing the console with other drivers including
16 the system driver. However, modular drivers cannot take over the console
17 that is currently occupied by another modular driver. (Exception: Drivers that
19 of driver occupying the consoles.) They can only take over the console that is
20 occupied by the system driver. In the same token, if the modular driver is
21 released by the console, the system driver will take over.
25 do_take_over_console() - load and bind driver to console layer
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 2 Driver Binding
5 Driver binding is the process of associating a device with a device
6 driver that can control it. Bus drivers have typically handled this
8 devices and the drivers. With generic device and device driver
19 for a driver, it is inserted at the end of this list. These are the
20 two events which trigger driver binding.
28 ID of the device must match one of the device IDs that the driver
31 algorithm, it is up to the bus driver to provide a callback to compare
32 a device against the IDs of a driver. The bus returns 1 if a match was
37 If a match is found, the device's driver field is set to the driver
[all …]
|
| D | porting.rst | 2 Porting Drivers to the New Driver Model
12 Please refer to `Documentation/driver-api/driver-model/*.rst` for definitions of
13 various driver types and concepts.
16 at the bus driver layer. This was intentional, to minimize the
20 In a nutshell, the driver model consists of a set of objects that can
24 The generic objects must be registered with the driver model core. By
36 Step 1: Registering the bus driver.
39 - Define a struct bus_type for the bus driver::
59 The bus type may be unregistered (if the bus driver may be compiled
128 bus driver should initialize the generic device. The most important
[all …]
|
| D | driver.rst | 11 be multiple devices in a system that a driver supports, struct
12 device_driver represents the driver as a whole (not a particular
18 The driver must initialize at least the name and bus fields. It should
28 driver. This declaration is hypothetical only; it relies on the driver
45 The most common example of this are device ID structures. A driver
52 the definition of the bus-specific driver. Like this::
56 struct device_driver driver;
60 (using the eepro100 driver again)::
64 .driver = {
84 The driver registers the structure on startup. For drivers that have
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 3 The pvrusb2 driver
11 This driver is intended for the "Hauppauge WinTV PVR USB 2.0", which
12 is a USB 2.0 hosted TV Tuner. This driver is a work in progress.
18 create a video4linux compatible driver. I began with Aurelien's
19 last known snapshot and evolved the driver to the state it is in
22 More information on this driver can be found at:
26 This driver has a strong separation of layers. They are very
34 3. High level hardware driver implementation which coordinates all
37 4. A "context" layer which manages instancing of driver, setup,
42 5. High level interfaces which glue the driver to various published
[all …]
|
| /Documentation/PCI/ |
| D | pciebus-howto.rst | 5 The PCI Express Port Bus Driver Guide HOWTO
14 This guide describes the basics of the PCI Express Port Bus driver
16 register/unregister with the PCI Express Port Bus Driver.
19 What is the PCI Express Port Bus Driver
37 be handled by a single complex driver or be individually distributed
40 Why use the PCI Express Port Bus Driver?
43 In existing Linux kernels, the Linux Device Driver Model allows a
44 physical device to be handled by only a single driver. The PCI
47 may have its own software service driver. In this case several
50 driver is loaded first, it claims a PCI-PCI Bridge Root Port. The
[all …]
|
| /Documentation/usb/ |
| D | gadget_serial.rst | 2 Linux Gadget Serial Driver v2.0
27 This document and the gadget serial driver itself are
30 If you have questions, problems, or suggestions for this driver
36 Versions of the gadget serial driver are available for the
38 version 2.3 or later of the gadget serial driver in a 2.6
47 With version 2.3 of the driver, major and minor device nodes are
56 The gadget serial driver is a Linux USB gadget driver, a USB device
57 side driver. It runs on a Linux system that has USB device side
61 The gadget serial driver talks over USB to either a CDC ACM driver
62 or a generic USB serial driver running on a host PC::
[all …]
|
| D | usb-serial.rst | 8 The USB serial driver currently supports a number of different USB to
19 Currently the driver can handle up to 256 different serial interfaces at
22 The major number that the driver uses is 188 so to use the driver,
35 When the device is connected and recognized by the driver, the driver
50 The driver is officially supported by Connect Tech Inc.
53 For any questions or problems with this driver, please contact
57 HandSpring Visor, Palm USB, and Clié USB driver
60 This driver works with all HandSpring USB, Palm USB, and Sony Clié USB
66 possible. The driver cleans up properly when the device is removed, or
95 There is a webpage and mailing lists for this portion of the driver at:
[all …]
|
| /Documentation/PCI/endpoint/ |
| D | pci-endpoint.rst | 6 endpoint controller driver, endpoint function driver, and using configfs
7 interface to bind the function driver to the controller driver.
14 assign memory resources and IRQ resources, load PCI driver (based on
35 in endpoint mode. It also provides APIs to be used by function driver/library
38 APIs for the PCI controller Driver
42 by the PCI controller driver.
46 The PCI controller driver should implement the following ops:
57 The PCI controller driver can then create a new EPC device by invoking
62 The PCI controller driver can destroy the EPC device created by either
70 driver should invoke pci_epc_linkup().
[all …]
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 2 Dell Remote BIOS Update driver (dell_rbu)
8 Document demonstrating the use of the Dell Remote BIOS Update driver
14 This document discusses the functionality of the rbu driver only.
21 This driver works with Dell OpenManage or Dell Update Packages for updating
31 Dell_RBU driver supports BIOS update using the monolithic image and packetized
32 image methods. In case of monolithic the driver allocates a contiguous chunk
34 using the driver breaks the image in to packets of fixed sizes and the driver
35 would place each packet in contiguous physical memory. The driver also
38 If the dell_rbu driver is unloaded all the allocated memory is freed.
40 The rbu driver needs to have an application (as mentioned above) which will
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-vdpa | 6 to a driver after the creation. It initially contains 1, which
8 driver immediately after they are created.
18 devices to a compatible driver.
27 Writing a device name to this file will cause the driver to
35 Writing a device name to this file will cause the driver to
43 This file allows the driver for a device to be specified.
44 When specified, only a driver with a name matching the value
51 device from its current driver or make any attempt to
52 automatically load the specified driver. If no driver with a
54 not bind to any driver. This also allows devices to opt-out of
[all …]
|
| D | sysfs-bus-amba | 5 This file allows the driver for a device to be specified which
7 When specified, only a driver with a name matching the value
14 device from its current driver or make any attempt to
15 automatically load the specified driver. If no driver with a
17 not bind to any driver. This also allows devices to opt-out of
18 driver binding using a driver_override name such as "none".
19 Only a single driver may be specified in the override, there is
|
| D | sysfs-bus-vmbus | 5 This file allows the driver for a device to be specified which
7 specified, only a driver with a name matching the value written
14 device from its current driver or make any attempt to
15 automatically load the specified driver. If no driver with a
17 will not bind to any driver. This also allows devices to
18 opt-out of driver binding using a driver_override name such as
19 "none". Only a single driver may be specified in the override,
|
| /Documentation/i2c/ |
| D | old-module-parameters.rst | 2 I2C device driver binding control from user-space in old kernels
12 control how the driver would probe I2C buses and attach to devices. These
13 parameters were known as ``probe`` (to let the driver probe for an extra
14 address), ``force`` (to forcibly attach the driver to a given device) and
15 ``ignore`` (to prevent a driver from probing a given address).
17 With the conversion of the I2C subsystem to the standard device driver
26 Attaching a driver to an I2C device
31 # modprobe <driver> probe=1,0x2d
32 # modprobe <driver> force=1,0x2d
33 # modprobe <driver> force_<device>=1,0x2d
[all …]
|
| /Documentation/scsi/ |
| D | advansys.rst | 4 AdvanSys Driver Notes
15 cache and board LRAM. A CDB is a single SCSI command. The driver
17 adapter detected. The number of CDBs used by the driver can be
64 Driver Compile Time Options and Debugging
69 1. ADVANSYS_ASSERT - Enable driver assertions (Def: Enabled)
72 driver. If an assertion fails a message will be displayed to
75 responsible for the driver. Assertion statements may proactively
76 detect problems with the driver and facilitate fixing these
78 execution of the driver.
80 2. ADVANSYS_DEBUG - Enable driver debugging (Def: Disabled)
[all …]
|
| D | lpfc.rst | 4 LPFC Driver Release Notes
10 Starting in the 8.0.17 release, the driver began to be targeted strictly
12 (pre 2.6.10). The 8.0.16 release should be used if the driver is to be
20 The driver now requires a 2.6.12 (if pre-release, 2.6.12-rc1) or later
27 history of the driver as we push for upstream acceptance.
31 In older revisions of the lpfc driver, the driver internally queued i/o
34 being removed, a switch rebooting, or a device reboot), the driver could
38 to the system. If the driver did not hide these conditions, i/o would be
39 errored by the driver, the mid-layer would exhaust its retries, and the
49 As a potential new addition to kernel.org, the 8.x driver was asked to
[all …]
|
| D | smartpqi.rst | 4 SMARTPQI - Microchip Smart Storage SCSI driver
7 This file describes the smartpqi SCSI driver for Microchip
8 (http://www.microchip.com) PQI controllers. The smartpqi driver
9 is the next generation SCSI driver for Microchip Corp. The smartpqi
10 driver is the first SCSI driver to implement the PQI queuing model.
12 The smartpqi driver will replace the aacraid driver for Adaptec Series 9
14 Series 9 controller will have to configure the smartpqi driver or their
17 For Microchip smartpqi controller support, enable the smartpqi driver
38 attribute will trigger the driver to scan for new, changed, or removed
41 The version attribute is read-only and will return the driver version
[all …]
|
| D | hpsa.rst | 4 HPSA - Hewlett Packard Smart Array driver
7 This file describes the hpsa SCSI driver for HP Smart Array controllers.
8 The hpsa driver is intended to supplant the cciss driver for newer
9 Smart Array controllers. The hpsa driver is a SCSI driver, while the
10 cciss driver is a "block" driver. Actually cciss is both a block
11 driver (for logical drives) AND a SCSI driver (for tape drives). This
12 "split-brained" design of the cciss driver is a source of excess
28 Additionally, older Smart Arrays may work with the hpsa driver if the kernel
30 nor supported by HP with this driver. For older Smart Arrays, the cciss
31 driver should still be used.
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-params.rst | 7 ``devlink`` provides capability for a driver to expose device parameters for low
13 across multiple drivers. Each driver is also free to add their own
14 parameters. Each driver must document the specific parameters they support,
28 - set while the driver is running, and takes effect immediately. No
31 - applied while the driver initializes. Requires the user to restart
32 the driver using the ``devlink`` reload command.
40 In order for ``driverinit`` parameters to take effect, the driver must
42 request a reload of the device driver.
49 add. Use of generic parameters is preferred over each driver creating their
81 Load firmware version preferred by the driver.
[all …]
|
| /Documentation/networking/device_drivers/ethernet/amd/ |
| D | pds_vfio_pci.rst | 5 PCI VFIO driver for the AMD/Pensando(R) DSC adapter family
8 AMD/Pensando Linux VFIO PCI Device Driver
14 The ``pds-vfio-pci`` module is a PCI driver that supports Live Migration
21 depends on the ``pds_core`` driver to create and enable SR-IOV Virtual
24 Shown below are the steps to bind the driver to a VF and also to the
25 associated auxiliary device created by the ``pds_core`` driver. This
38 # Prevent non-vfio VF driver from probing the VF device
44 # Allow the VF to be bound to the pds-vfio-pci driver
47 # Bind the VF to the pds-vfio-pci driver
54 Enabling the driver
[all …]
|
| /Documentation/wmi/ |
| D | driver-development-guide.rst | 4 WMI driver development guide
7 The WMI subsystem provides a rich driver API for implementing WMI drivers,
8 documented at Documentation/driver-api/wmi.rst. This document will serve
9 as an introductory guide for WMI driver writers using this API. It is supposed
16 Before developing an WMI driver, information about the WMI device in question
30 The ``wmi-bmof`` driver exposes this information to userspace, see
44 Basic WMI driver structure
47 The basic WMI driver is build around the struct wmi_driver, which is then bound
59 .driver = {
73 The probe() callback is called when the WMI driver is bound to a matching WMI device. Allocating
[all …]
|
| /Documentation/mhi/ |
| D | topology.rst | 13 MHI controller driver manages the interaction with the MHI client devices
17 is taken care by the physical bus such as PCIe. Each controller driver exposes
20 Below are the roles of the MHI controller driver:
42 MHI Driver
45 MHI driver is the client driver which binds to one or more MHI devices. The MHI
46 driver sends and receives the upper-layer protocol packets like IP packets,
48 bind the MHI devices to the MHI driver.
50 Each supported driver is enumerated in::
54 Below are the roles of the MHI driver:
56 * Registers the driver with the MHI bus framework using mhi_driver_register.
|
| /Documentation/power/ |
| D | drivers-testing.rst | 11 resume transitions in a driver, it is necessary to suspend and resume a fully
12 functional system with this driver loaded. Moreover, that should be done
19 resume without the driver being tested. Thus, if possible, you should first
21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
24 2. Testing the driver
28 without the new driver, you are ready to test it:
30 a) Build the driver as a module, load it and try the test modes of hibernation
33 b) Load the driver and attempt to hibernate in the "reboot", "shutdown" and
36 c) Compile the driver directly into the kernel and try the test modes of
39 d) Attempt to hibernate with the driver compiled directly into the kernel
[all …]
|
| /Documentation/hwmon/ |
| D | mp9941.rst | 3 Kernel driver mp9941
22 This driver implements support for Monolithic Power Systems, Inc. (MPS)
29 The driver exports the following attributes via the 'sysfs' files
40 The driver provides the following attributes for output voltage:
54 The driver provides the following attributes for input current:
64 The driver provides the following attributes for output current:
70 The driver provides the following attributes for input power:
76 The driver provides the following attributes for output power:
82 The driver provides the following attributes for temperature:
|
12345678910>>...98