| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | atmioc.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
2 /* atmioc.h - ranges for ATM-related ioctl numbers */
4 /* Written 1995-1999 by Werner Almesberger, EPFL LRC/ICA */
8 * See https://icawww1.epfl.ch/linux-atm/magic.html for the complete list of
19 #define ATMIOC_PHYCOM 0x00 /* PHY device common ioctls, globally unique */
21 #define ATMIOC_PHYTYP 0x10 /* PHY dev type ioctls, unique per PHY type */
23 #define ATMIOC_PHYPRV 0x30 /* PHY dev private ioctls, unique per driver */
25 #define ATMIOC_SARCOM 0x50 /* SAR device common ioctls, globally unique */
27 #define ATMIOC_SARPRV 0x60 /* SAR dev private ioctls, unique per driver */
29 #define ATMIOC_ITF 0x80 /* Interface ioctls, globally unique */
[all …]
|
| /kernel/linux/linux-4.19/include/uapi/linux/ |
| D | atmioc.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
2 /* atmioc.h - ranges for ATM-related ioctl numbers */
4 /* Written 1995-1999 by Werner Almesberger, EPFL LRC/ICA */
8 * See http://icawww1.epfl.ch/linux-atm/magic.html for the complete list of
19 #define ATMIOC_PHYCOM 0x00 /* PHY device common ioctls, globally unique */
21 #define ATMIOC_PHYTYP 0x10 /* PHY dev type ioctls, unique per PHY type */
23 #define ATMIOC_PHYPRV 0x30 /* PHY dev private ioctls, unique per driver */
25 #define ATMIOC_SARCOM 0x50 /* SAR device common ioctls, globally unique */
27 #define ATMIOC_SARPRV 0x60 /* SAR dev private ioctls, unique per driver */
29 #define ATMIOC_ITF 0x80 /* Interface ioctls, globally unique */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-g-topology.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 MEDIA_IOC_G_TOPOLOGY - Enumerate the graph topology and graph element properties
53 .. flat-table:: struct media_v2_topology
54 :header-rows: 0
55 :stub-columns: 0
58 * - __u64
59 - ``topology_version``
60 - Version of the media graph topology. When the graph is created,
64 * - __u32
65 - ``num_entities``
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/mediactl/ |
| D | media-ioc-g-topology.rst | 1 .. -*- coding: utf-8; mode: rst -*-
12 MEDIA_IOC_G_TOPOLOGY - Enumerate the graph topology and graph element properties
26 File descriptor returned by :ref:`open() <media-func-open>`.
53 .. flat-table:: struct media_v2_topology
54 :header-rows: 0
55 :stub-columns: 0
58 * - __u64
59 - ``topology_version``
60 - Version of the media graph topology. When the graph is created,
64 * - __u32
[all …]
|
| /kernel/linux/linux-5.10/drivers/virt/nitro_enclaves/ |
| D | ne_pci_dev.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
17 * DOC: Nitro Enclaves (NE) PCI device
21 * PCI_DEVICE_ID_NE - Nitro Enclaves PCI device id.
25 * PCI_BAR_NE - Nitro Enclaves PCI device MMIO BAR.
30 * DOC: Device registers in the NE PCI device MMIO BAR
34 * NE_ENABLE - (1 byte) Register to notify the device that the driver is using
42 * NE_VERSION - (2 bytes) Register to select the device run-time version
49 * NE_COMMAND - (4 bytes) Register to notify the device what command was
50 * requested (Write-Only).
55 * NE_EVTCNT - (4 bytes) Register to notify the driver that a reply or a device
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-info.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
7 The ``devlink-info`` mechanism enables device drivers to report device
10 The original motivation for the ``devlink-info`` API was twofold:
12 - making it possible to automate device and firmware management in a fleet
13 of machines in a vendor-independent fashion (see also
14 :ref:`Documentation/networking/devlink/devlink-flash.rst <devlink_flash>`);
15 - name the per component FW versions (as opposed to the crowded ethtool
18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver
19 versions is generally discouraged - here, and via any other Linux API.
21 .. list-table:: List of top level info objects
[all …]
|
| D | ice.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 device driver.
15 .. list-table:: devlink info versions implemented
18 * - Name
19 - Type
20 - Example
21 - Description
22 * - ``board.id``
23 - fixed
24 - K65390-000
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-bus-rbd | 6 (WO) Add rbd block device.
12 The snapshot name can be "-" or omitted to map the image
13 read/write. A <dev-id> will be assigned for any registered block
14 device. If snapshot is used, it will be mapped read-only.
22 (WO) Remove rbd block device.
24 Usage: <dev-id> [force]
72 What: /sys/bus/rbd/devices/<dev-id>/size
73 What: /sys/bus/rbd/devices/<dev-id>/major
74 What: /sys/bus/rbd/devices/<dev-id>/client_id
75 What: /sys/bus/rbd/devices/<dev-id>/pool
[all …]
|
| D | sysfs-class-net | 20 2: stolen from another device
29 Values vary based on the lower-level protocol used by the
48 01-80-C2-00-00-0X on a bridge device. Only values that set bits
54 0: 01-80-C2-00-00-00 Bridge Group Address used for STP
55 1: 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE
56 2: 01-80-C2-00-00-02 (Link Aggregation) 802.3ad
59 care when forwarding control frames e.g. 802.1X-PAE or LLDP.
89 Indicates the device unique identifier. Format is an hexadecimal
92 address as their parent device.
105 the device is not usable unless some supplicant-based
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_ioctl.c | 58 * - GET_UNIQUE ioctl, implemented by drm_getunique is wrapped up in libdrm
60 * - The libdrm drmSetBusid function is backed by the SET_UNIQUE ioctl. All
62 * - The internal set_busid kernel functions and driver callbacks are
65 * - Other ioctls and functions involved are named consistently.
72 * Now the actual horror story of how device lookup in drm works. At large,
73 * there's 2 different ways, either by busid, or by device driver name.
78 * side-effect this fills out the unique name in the master structure.
79 * 2. Call GET_UNIQUE to read out the unique name from the master structure,
81 * the next device node.
87 * means the the unique name for the master node just opening is _not_ filled
[all …]
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/ |
| D | drm_ioctl.c | 52 * - GET_UNIQUE ioctl, implemented by drm_getunique is wrapped up in libdrm
54 * - The libdrm drmSetBusid function is backed by the SET_UNIQUE ioctl. All
56 * - The internal set_busid kernel functions and driver callbacks are
59 * - Other ioctls and functions involved are named consistently.
66 * Now the actual horror story of how device lookup in drm works. At large,
67 * there's 2 different ways, either by busid, or by device driver name.
72 * side-effect this fills out the unique name in the master structure.
73 * 2. Call GET_UNIQUE to read out the unique name from the master structure,
75 * the next device node.
81 * means the the unique name for the master node just opening is _not_ filled
[all …]
|
| D | drm_drv.c | 74 * prefer to embed struct drm_device into their own device
85 * A DRM device can provide several char-dev interfaces on the DRM-Major. Each
87 * of the device-driver, different interfaces are registered.
89 * Minors can be accessed via dev->$minor_name. This pointer is either
90 * NULL or a valid drm_minor pointer and stays valid as long as the device is
91 * valid. This means, DRM minors have the same life-time as the underlying
92 * device. However, this doesn't mean that the minor is active. Minors are
93 * registered and unregistered dynamically according to device-state.
101 return &dev->primary; in drm_minor_get_slot()
103 return &dev->render; in drm_minor_get_slot()
[all …]
|
| /kernel/linux/linux-5.10/drivers/message/fusion/ |
| D | mptsas.h | 3 * High performance SCSI + LAN / Fibre Channel device drivers.
8 * Copyright (c) 1999-2008 LSI Corporation
9 * (mailto:DL-MPTFusionLinux@lsi.com)
12 /*=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=*/
26 LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
45 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
50 /*{-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=*/
90 /* cached data for a removed device */
103 u8 phys_disk_num; /* hrc - unique index*/
130 u16 handle; /* unique id to address this device */
[all …]
|
| /kernel/linux/linux-4.19/drivers/message/fusion/ |
| D | mptsas.h | 3 * High performance SCSI + LAN / Fibre Channel device drivers.
8 * Copyright (c) 1999-2008 LSI Corporation
9 * (mailto:DL-MPTFusionLinux@lsi.com)
12 /*=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=*/
26 LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
45 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
50 /*{-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=*/
90 /* cached data for a removed device */
103 u8 phys_disk_num; /* hrc - unique index*/
130 u16 handle; /* unique id to address this device */
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | fsl_devices.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
5 * Definitions for any platform device related flags or structures for
17 PHY CLK to become stable - 10ms*/
25 * unique device: a platform_device entry in fsl_plat_devs[] plus
26 * associated device information in its platform_data structure.
28 * A chip is described by a set of unique devices.
30 * Each sub-arch has its own master list of unique devices and
31 * enumerates them by enum fsl_devices in a sub-arch specific header
34 * first is device specific information that help identify any
35 * unique features of a peripheral. The second is any
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | fsl_devices.h | 4 * Definitions for any platform device related flags or structures for
21 PHY CLK to become stable - 10ms*/
29 * unique device: a platform_device entry in fsl_plat_devs[] plus
30 * associated device information in its platform_data structure.
32 * A chip is described by a set of unique devices.
34 * Each sub-arch has its own master list of unique devices and
35 * enumerates them by enum fsl_devices in a sub-arch specific header
38 * first is device specific information that help identify any
39 * unique features of a peripheral. The second is any
40 * information that may be defined by the board or how the device
[all …]
|
| /kernel/linux/linux-4.19/include/drm/ |
| D | drm_auth.h | 49 * struct drm_master - drm master structure
52 * @dev: Link back to the DRM device
54 * @driver_priv: Pointer to driver-private information.
62 * Note that master structures are only relevant for the legacy/primary device
63 * nodes, hence there can only be one per device, not one per drm_minor.
69 * @unique: Unique identifier: e.g. busid. Protected by
72 char *unique; member
74 * @unique_len: Length of unique field. Protected by
|
| /kernel/linux/linux-5.10/include/media/ |
| D | media-device.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Media device
17 #include <media/media-devnode.h>
18 #include <media/media-entity.h>
21 struct device;
25 * struct media_entity_notify - Media Entity Notify
32 * registered with the media device. This handler is intended for creating
43 * struct media_device_ops - Media device operations
75 * struct media_device - Media device
76 * @dev: Parent device
[all …]
|
| /kernel/linux/linux-5.10/include/drm/ |
| D | drm_auth.h | 56 * struct drm_master - drm master structure
59 * @dev: Link back to the DRM device
60 * @driver_priv: Pointer to driver-private information.
68 * Note that master structures are only relevant for the legacy/primary device
69 * nodes, hence there can only be one per device, not one per drm_minor.
75 * @unique: Unique identifier: e.g. busid. Protected by
78 char *unique; member
80 * @unique_len: Length of unique field. Protected by
|
| /kernel/linux/linux-4.19/include/media/ |
| D | media-device.h | 2 * Media device
25 #include <media/media-devnode.h>
26 #include <media/media-entity.h>
29 struct device;
32 * struct media_entity_notify - Media Entity Notify
39 * registered with the media device. This handler is intended for creating
50 * struct media_device_ops - Media device operations
60 * struct media_device - Media device
61 * @dev: Parent device
62 * @devnode: Media device node
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/ |
| D | csi_rx_public.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
27 * Get the state of the csi rx frontend regiester-set.
29 * @param[in] id The global unique ID of the csi rx fe controller.
30 * @param[out] state Point to the register-state.
37 * Dump the state of the csi rx frontend regiester-set.
39 * @param[in] id The global unique ID of the csi rx fe controller.
40 * @param[in] state Point to the register-state.
49 * @param[in] id The global unique ID of the input-buffer controller.
59 * Get the state of the csi rx backend regiester-set.
61 * @param[in] id The global unique ID of the csi rx be controller.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-rbd | 6 (WO) Add rbd block device.
14 The snapshot name can be "-" or omitted to map the image
15 read/write. A <dev-id> will be assigned for any registered block
16 device. If snapshot is used, it will be mapped read-only.
24 (WO) Remove rbd block device.
26 Usage: <dev-id> [force]
76 What: /sys/bus/rbd/devices/<dev-id>/size
77 What: /sys/bus/rbd/devices/<dev-id>/major
78 What: /sys/bus/rbd/devices/<dev-id>/client_id
79 What: /sys/bus/rbd/devices/<dev-id>/pool
[all …]
|
| /kernel/linux/linux-4.19/drivers/target/ |
| D | target_core_rd.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
35 /* Unique Ramdisk Device ID in Ramdisk HBA */
37 /* Total page count for ramdisk device */
47 /* Ramdisk HBA device is connected to */
53 u32 rd_host_id; /* Unique Ramdisk Host ID */
|
| /kernel/linux/linux-5.10/drivers/target/ |
| D | target_core_rd.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
35 /* Unique Ramdisk Device ID in Ramdisk HBA */
37 /* Total page count for ramdisk device */
47 /* Ramdisk HBA device is connected to */
53 u32 rd_host_id; /* Unique Ramdisk Host ID */
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/input/ |
| D | omap-keypad.txt | 1 * TI's Keypad Controller device tree bindings
3 TI's Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
5 A key can be placed at each intersection of a unique row and a unique column.
6 The keypad controller can sense a key-press and key-release and report the
9 This binding is based on the matrix-keymap binding with the following
12 keypad,num-rows and keypad,num-columns are required.
15 - compatible: should be one of the following
16 - "ti,omap4-keypad": For controllers compatible with omap4 keypad
20 - linux,keypad-no-autorepeat: do no enable autorepeat feature.
[all …]
|