| /linux/Documentation/driver-api/driver-model/ |
| H A 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
42 model because the bus they belong to has a bus-specific structure with
43 bus-specific fields that cannot be generalized.
45 The most common example of this are device ID structures. A driver
48 completely bus-specific. Defining them as bus-specific entities would
49 sacrifice type-safety, so we keep bus-specific structures around.
51 Bus-specific drivers should include a generic struct device_driver in
[all …]
|
| H A 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
21 be embedded in larger, bus-specific objects. Fields in these generic
22 objects can replace fields in the bus-specific objects.
24 The generic objects must be registered with the driver model core. By
28 # mount -t sysfs sysfs /sys
36 Step 1: Registering the bus driver.
[all …]
|
| H A 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
7 because there have been bus-specific structures to represent the
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
29 supports. The format and semantics for comparing IDs is bus-specific.
31 algorithm, it is up to the bus driver to provide a callback to compare
[all …]
|
| /linux/drivers/net/ethernet/intel/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
15 your specific card in the following questions.
27 This driver supports Intel(R) PRO/100 family of adapters.
30 in the format 123456-001 (six digits hyphen three digits).
32 Use the above information and the Adapter & Driver ID Guide that
39 More specific information on configuring the driver is in
42 To compile this driver as a module, choose M here. The module
49 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
51 to the Adapter & Driver ID Guide that can be located at:
55 More specific information on configuring the driver is in
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H A D | typec_bus.rst | 2 API for USB Type-C Alternate Mode drivers
6 ------------
9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications.
10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
11 every alternate mode, so every alternate mode will need a custom driver.
13 USB Type-C bus allows binding a driver to the discovered partner alternate
16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate
24 matching SVID and mode. Communication between the port driver and alternate mode
25 driver will happen using the same API.
29 specific commands from the alternate mode drivers to the partner, and from the
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-fm-tx.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _fm-tx-controls:
16 .. _fm-tx-control-id:
28 step are driver-specific.
35 to 31 pre-defined programme types.
53 programme-related information or any other text. In these cases,
104 receiver-generated distortion and prevent overmodulation.
108 microseconds. Step and range are driver-specific.
112 are driver-specific.
122 range and step are driver-specific.
[all …]
|
| H A D | ext-ctrls-rf-tuner.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _rf-tuner-controls:
17 called Zero-IF tuners. Older tuners were typically simple PLL tuners
29 .. _rf-tuner-control-id:
41 automatic mode bandwidth configuration is performed by the driver.
45 to receiving party needs. Driver configures filters to fulfill
48 range and step are driver-specific.
65 range and step are driver-specific.
73 driver-specific.
77 located inside mixer block, where RF signal is down-converted by the
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | vfio-pci-device-specific-driver-acceptance.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Acceptance criteria for vfio-pci device specific driver variants
7 --------
8 The vfio-pci driver exists as a device agnostic driver using the
11 vfio-pci driver does include some device specific support, further
12 extensions for yet more advanced device specific features are not
13 sustainable. The vfio-pci driver has therefore split out
14 vfio-pci-core as a library that may be reused to implement features
15 requiring device specific knowledge, ex. saving and loading device
18 In support of such features, it's expected that some device specific
[all …]
|
| /linux/drivers/bcma/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
8 tristate "Broadcom specific AMBA"
11 Bus driver for Broadcom specific Advanced Microcontroller Bus
16 # Support for Block-I/O. SELECT this from the driver that needs it.
26 bool "Support for BCMA on PCI-host bus"
42 bool "BCMA Broadcom PCI core driver"
46 BCMA bus may have many versions of PCIe core. This driver
54 This driver is also prerequisite for a hostmode PCIe core
58 bool "Driver for PCI core working in hostmode"
64 bool "BCMA Broadcom MIPS core driver"
[all …]
|
| /linux/drivers/net/ethernet/wangxun/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
15 be asked for your specific card in the following questions.
34 This driver supports Wangxun(R) GbE PCI Express family of
37 More specific information on configuring the driver is in
40 To compile this driver as a module, choose M here. The module
58 This driver supports Wangxun(R) 10/25/40GbE PCI Express family of
61 More specific information on configuring the driver is in
64 To compile this driver as a module, choose M here. The module
74 This driver supports virtual functions for SP1000A, WX1820AL,
77 This driver was formerly named txgbevf.
[all …]
|
| /linux/Documentation/driver-api/rapidio/ |
| H A D | mport_cdev.rst | 2 RapidIO subsystem mport character device driver (rio_mport_cdev.c)
8 This device driver is the result of collaboration within the RapidIO.org
12 character mode driver interface which exposes the capabilities of RapidIO
16 This driver (MPORT_CDEV) provides access to basic RapidIO subsystem operations
17 for user-space applications. Most of RapidIO operations are supported through
20 When loaded this device driver creates filesystem nodes named rio_mportX in /dev
24 Using available set of ioctl commands user-space applications can perform
27 - Reads and writes from/to configuration registers of mport devices
29 - Reads and writes from/to configuration registers of remote RapidIO devices.
32 - Set RapidIO Destination ID for mport devices (RIO_MPORT_MAINT_HDID_SET)
[all …]
|
| /linux/Documentation/networking/devlink/ |
| H A D | netdevsim.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ``netdevsim`` device driver.
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 * - ``max_macs``
18 - driverinit
20 The ``netdevsim`` driver also implements the following driver-specific
23 .. list-table:: Driver-specific parameters implemented
26 * - Name
[all …]
|
| H A D | mlxsw.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 device driver.
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 * - ``fw_load_policy``
18 - driverinit
20 The ``mlxsw`` driver also implements the following driver-specific
23 .. list-table:: Driver-specific parameters implemented
26 * - Name
[all …]
|
| H A D | devlink-dpipe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 ``devlink-dpipe`` provides a standardized way to provide visibility into the
34 Level Path Compression trie (LPC-trie) in hardware.
45 The ``devlink-dpipe`` interface closes this gap. The hardware's pipeline is
46 modeled as a graph of match/action tables. Each table represents a specific
50 configuration, but the ``devlink-dpipe`` interface uses it for visibility
52 ``devlink-dpipe`` should change according to the changes done by the
75 the actual content of a specific table.
77 The hardware pipeline is not port specific, but rather describes the whole
84 ``devlink-dpipe`` generally is not intended for configuration. The exception
[all …]
|
| /linux/rust/kernel/ |
| H A D | driver.rs | 1 // SPDX-License-Identifier: GPL-2.0
5 //! This documentation describes how to implement a bus specific driver API and how to align it with
6 //! the design of (bus specific) devices.
11 //! # Driver Trait
13 //! The main driver interface is defined by a bus specific driver trait. For instance:
16 //! pub trait Driver: Send {
17 //! /// The type holding information about each device ID supported by the driver.
20 //! /// The table of OF device ids supported by the driver.
23 //! /// The table of ACPI device ids supported by the driver.
26 //! /// Driver probe.
[all …]
|
| /linux/include/linux/device/ |
| H A D | driver.h | 1 // SPDX-License-Identifier: GPL-2.0
3 * The driver-specific portions of the driver model
5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
6 * Copyright (c) 2004-2009 Greg Kroah-Hartman <gregkh@suse.de>
7 * Copyright (c) 2008-2009 Novell Inc.
8 * Copyright (c) 2012-2019 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
9 * Copyright (c) 2012-2019 Linux Foundation
11 * See Documentation/driver-api/driver-model/ for more information.
24 * enum probe_type - device driver probe type to try
35 * their probe routines to run synchronously with driver and
[all …]
|
| H A D | bus.h | 1 // SPDX-License-Identifier: GPL-2.0
3 * bus.h - the bus-specific portions of the driver model
5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
6 * Copyright (c) 2004-2009 Greg Kroah-Hartman <gregkh@suse.de>
7 * Copyright (c) 2008-2009 Novell Inc.
8 * Copyright (c) 2012-2019 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
9 * Copyright (c) 2012-2019 Linux Foundation
11 * See Documentation/driver-api/driver-model/ for more information.
25 * struct bus_type - The bus type of the device
28 * @dev_name: Used for subsystems to enumerate devices like ("foo%u", dev->id).
[all …]
|
| /linux/Documentation/scsi/ |
| H A D | hpsa.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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
19 - Smart Array P212
20 - Smart Array P410
[all …]
|
| /linux/Documentation/driver-api/pldmfw/ |
| H A D | driver-ops.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
4 Driver-specific callbacks
7 The ``pldmfw`` module relies on the device driver for implementing device
8 specific behavior using the following operations.
11 -----------------
23 ----------------------
25 The ``.send_package_data`` operation is used to send the device-specific
29 length. The device driver should send this data to firmware.
32 -------------------------
37 device driver should send the component information to the device firmware,
[all …]
|
| /linux/Documentation/arch/s390/ |
| H A D | cds.rst | 6 Device Driver I/O Support Routines
9 - Ingo Adlung
10 - Cornelia Huck
12 Copyright, IBM Corp. 1999-2002
21 processing, shared versus non-shared interrupt processing, DMA versus port
23 either every single device driver needs to implement the hardware I/O
26 every single device driver would have to provide itself.
30 Operation manual (IBM Form. No. SA22-7201).
37 below. Some of them implement common Linux device driver interfaces, while
38 some of them are ESA/390 platform specific.
[all …]
|
| /linux/include/linux/platform_data/ |
| H A D | brcmfmac.h | 27 * Platform specific driver functions and data. Through the platform specific
28 * device data functions and data can be provided to help the brcmfmac driver to
34 * Note: the brcmfmac can be loaded as module or be statically built-in into
35 * the kernel. If built-in then do note that it uses module_init (and
37 * create a module with the platform specific data for the brcmfmac and have
38 * it built-in to the kernel then use a higher initcall then device_initcall
42 * When the driver does not "detect" platform driver data then it will continue
48 * enum brcmf_bus_type - Bus type identifier. Currently SDIO, USB and PCIE are
59 * struct brcmfmac_sdio_pd - SDIO Device specific platform data.
61 * @txglomsz: SDIO txglom size. Use 0 if default of driver is to be
[all …]
|
| /linux/drivers/thunderbolt/ |
| H A D | nhi.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Thunderbolt driver - NHI driver
34 * struct tb_nhi_ops - NHI specific optional operations
35 * @init: NHI specific initialization
36 * @suspend_noirq: NHI specific suspend_noirq hook
37 * @resume_noirq: NHI specific resume_noirq hook
38 * @runtime_suspend: NHI specific runtime_suspend hook
39 * @runtime_resume: NHI specific runtime_resume hook
40 * @shutdown: NHI specific shutdown
54 * PCI IDs used in this driver from Win Ridge forward. There is no
|
| /linux/include/linux/ |
| H A D | platform_device.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * platform_device.h - generic, centralized driver model
5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
7 * See Documentation/driver-api/driver-model/ for more information.
15 #define PLATFORM_DEVID_NONE (-1)
16 #define PLATFORM_DEVID_AUTO (-2)
38 /* arch specific additions */
42 #define platform_get_device_id(pdev) ((pdev)->id_entry)
44 #define dev_is_platform(dev) ((dev)->bus == &platform_bus_type)
78 return IOMEM_ERR_PTR(-EINVAL); in devm_platform_get_and_ioremap_resource()
[all …]
|
| /linux/Documentation/driver-api/virtio/ |
| H A D | virtio.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 to interface any compliant device (real or emulated) with a driver.
24 Device - Driver communication: virtqueues
29 using a specific transport method -- PCI, MMIO or CCW -- that is
34 The communication between the driver in the guest OS and the device in
40 .. kernel-doc:: include/uapi/linux/virtio_ring.h
49 the host device and the guest driver communicate.
56 .. kernel-doc:: include/linux/virtio.h
60 device has consumed the buffers provided by the driver. More
63 a virtqueue during the virtqueue setup process (transport-specific).
[all …]
|
| /linux/Documentation/i2c/ |
| H A D | fault-codes.rst | 10 ----------------------------------
14 some cases, such as re-initializing (and maybe resetting). After such
21 In short, your I2C driver code may need to know these codes in order
27 -------------------------
29 some positive number indicating a non-fault return. The specific
31 though most Linux systems use <asm-generic/errno*.h> numbering.
39 specific to their host bus (such as PCI, or the platform bus).
73 specific fault code when you can.
77 performing an I/O operation. Use a more specific fault
81 Returned by driver probe() methods. This is a bit more
[all …]
|