Searched +full:device +full:- +full:id (Results 1 – 25 of 1071) sorted by relevance
12345678910>>...43
| /Documentation/ABI/testing/ |
| D | sysfs-bus-cdx | 18 Vendor ID for this CDX device, in hexadecimal. Vendor ID is
19 16 bit identifier which is specific to the device manufacturer.
20 Combination of Vendor ID and Device ID identifies a device.
22 What: /sys/bus/cdx/devices/.../device
26 Device ID for this CDX device, in hexadecimal. Device ID is
27 16 bit identifier to identify a device type within the range
28 of a device manufacturer.
29 Combination of Vendor ID and Device ID identifies a device.
35 Subsystem Vendor ID for this CDX device, in hexadecimal.
36 Subsystem Vendor ID is 16 bit identifier specific to the
[all …]
|
| D | sysfs-bus-vfio-mdev | 1 What: /sys/.../<device>/mdev_supported_types/
6 supported mediated device types and their details for
7 <device>. Supported type attributes are defined by the
8 vendor driver who registers with Mediated device framework.
10 by adding the device driver string as a prefix to the
13 What: /sys/.../<device>/mdev_supported_types/<type-id>/
24 What: /sys/.../mdev_supported_types/<type-id>/create
28 Writing UUID to this file will create mediated device of
29 type <type-id> for parent device <device>. This is a
30 write-only file.
[all …]
|
| D | sysfs-bus-i3c | 1 What: /sys/bus/i3c/devices/i3c-<bus-id>
3 Contact: linux-i3c@vger.kernel.org
5 An I3C bus. This directory will contain one sub-directory per
6 I3C device present on the bus.
8 What: /sys/bus/i3c/devices/i3c-<bus-id>/current_master
10 Contact: linux-i3c@vger.kernel.org
12 Expose the master that owns the bus (<bus-id>-<master-pid>) at
17 What: /sys/bus/i3c/devices/i3c-<bus-id>/mode
19 Contact: linux-i3c@vger.kernel.org
21 I3C bus mode. Can be "pure", "mixed-fast" or "mixed-slow". See
[all …]
|
| D | sysfs-bus-pci | 4 Contact: linux-pci@vger.kernel.org
6 Writing a device location to this file will cause
7 the driver to attempt to bind to the device found at
10 That is Domain:Bus:Device.Function and is the same as
15 (Note: kernels before 2.6.28 may require echo -n).
20 Contact: linux-pci@vger.kernel.org
22 Writing a device location to this file will cause the
23 driver to attempt to unbind from the device found at
26 That is Domain:Bus:Device.Function and is the same as
31 (Note: kernels before 2.6.28 may require echo -n).
[all …]
|
| D | sysfs-block-zram | 1 What: /sys/block/zram<id>/disksize
5 The disksize file is read-write and specifies the disk size
10 What: /sys/block/zram<id>/initstate
14 The initstate file is read-only and shows the initialization
15 state of the device.
17 What: /sys/block/zram<id>/reset
21 The reset file is write-only and allows resetting the
22 device. The reset operation frees all the memory associated
23 with this device.
25 What: /sys/block/zram<id>/max_comp_streams
[all …]
|
| D | sysfs-driver-hid | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
2 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/report_descriptor
3 What: /sys/class/hidraw/hidraw<num>/device/report_descriptor
7 Description: When read, this file returns the device's raw binary HID
12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
13 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/country
14 What: /sys/class/hidraw/hidraw<num>/device/country
19 of the device's HID country code (e.g. 21 for US).
|
| D | sysfs-class-rapidio | 3 On-chip RapidIO controllers and PCIe-to-RapidIO bridges
7 subdirectories named as "rapidioN" where N = mport ID registered
10 NOTE: An mport ID is not a RapidIO destination ID assigned to a
11 given local mport device.
21 0 = small (8-bit destination ID, max. 256 devices),
23 1 = large (16-bit destination ID, max. 65536 devices).
32 (RO) reports RapidIO destination ID assigned to the given
33 RapidIO mport device. If value 0xFFFFFFFF is returned this means
34 that no valid destination ID have been assigned to the mport
36 only fabric enumerating mports have a valid destination ID
[all …]
|
| D | sysfs-class-pktcdvd | 2 ---------------
15 add (WO) Write a block device id (major:minor) to
16 create a new pktcdvd device and map it to the
17 block device.
19 remove (WO) Write the pktcdvd device id (major:minor)
20 to remove the pktcdvd device.
22 device_map (RO) Shows the device mapping in format:
23 pktcdvd[0-7] <pktdevid> <blkdevid>
27 What: /sys/class/pktcdvd/pktcdvd[0-7]/dev
28 What: /sys/class/pktcdvd/pktcdvd[0-7]/uevent
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | microchip,lan95xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/microchip,lan95xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Oleksij Rempel <o.rempel@pengutronix.de>
13 Device tree properties for hard wired SMSC95xx compatible USB Ethernet
17 - $ref: ethernet-controller.yaml#
22 - enum:
23 - usb424,9500 # SMSC9500 USB Ethernet Device
24 - usb424,9505 # SMSC9505 USB Ethernet Device
[all …]
|
| /Documentation/netlink/specs/ |
| D | dpll.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
8 -
16 -
20 -
23 render-max: true
24 -
26 name: lock-status
28 provides information of dpll device lock status, valid values for
31 -
37 -
[all …]
|
| D | netdev.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
9 -
11 name: xdp-act
12 render-max: true
14 -
19 -
23 -
24 name: ndo-xmit
27 -
28 name: xsk-zerocopy
[all …]
|
| /Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 1 # SPDX-License-Identifier: GPL-2.0
14 # Those symbols should not be used by uAPI - don't document them
171 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
172 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
173 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
174 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
175 replace define V4L2_CAP_VIDEO_M2M device-capabilities
176 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
177 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
178 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
[all …]
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 5 The RapidIO standard is a packet-based fabric interconnect standard designed for
8 is publicly available for download from the RTA web-site [1].
16 Because the RapidIO subsystem follows the Linux device model it is integrated
17 into the kernel similarly to other buses by defining RapidIO-specific device and
18 bus types and registering them within the device model.
21 architecture-specific interfaces that provide support for common RapidIO
33 ---------------
40 host device ID that is valid when a master port is configured as an enumerating
43 RapidIO master ports are serviced by subsystem specific mport device drivers
49 2.2 Device
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 8 This document describes a collection of device-mapper targets that
9 between them implement thin-provisioning and snapshots.
24 Metadata is stored on a separate device from data, giving the
27 - Improve metadata resilience by storing metadata on a mirrored volume
28 but data on a non-mirrored one.
30 - Improve performance by storing the metadata on SSD.
40 dm-devel@redhat.com with details and we'll try our best to improve
46 a Red Hat distribution it is named 'device-mapper-persistent-data').
52 They use the dmsetup program to control the device-mapper driver
53 directly. End users will be advised to use a higher-level volume
[all …]
|
| /Documentation/arch/s390/ |
| D | qeth.rst | 9 -------
11 To generate the events the device must be assigned a role of either
13 "z/VM Connectivity, SC24-6174".
16 of some configured Bridge Port device on the channel changes, a udev
18 ccwgroup device. The event has the following attributes:
21 indicates that the Bridge Port device changed
32 It is emitted on behalf of the corresponding ccwgroup device when a host
33 or a VLAN is registered or unregistered on the network served by the device.
42 VLAN=numeric-vlan-id
43 VLAN ID on which the event occurred. Not included
[all …]
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,k3-sci-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/keystone/ti,k3-sci-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common K3 TI-SCI
10 - Nishanth Menon <nm@ti.com>
14 that is responsible for managing various SoC-level resources like clocks,
16 through the TI-SCI protocol.
18 Each specific device management node like a clock controller node, a reset
19 controller node or an interrupt-controller node should define a common set
[all …]
|
| /Documentation/devicetree/bindings/virtio/ |
| D | virtio-device.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/virtio/virtio-device.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Virtio device
10 - Viresh Kumar <viresh.kumar@linaro.org>
19 pattern: "^virtio,device[0-9a-f]{1,8}$"
20 description: Virtio device nodes.
21 "virtio,deviceID", where ID is the virtio device id. The textual
22 representation of ID shall be in lower case hexadecimal with leading
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-device.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/usb-device.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic USB Device
10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org>
13 Usually, we only use device tree for hard wired USB device.
15 http://www.devicetree.org/open-firmware/bindings/usb/usb-1_0.ps
17 Four types of device-tree nodes are defined: "host-controller nodes"
18 representing USB host controllers, "device nodes" representing USB devices,
[all …]
|
| /Documentation/devicetree/bindings/i3c/ |
| D | i3c.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/i3c/i3c.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alexandre Belloni <alexandre.belloni@bootlin.com>
11 - Miquel Raynal <miquel.raynal@bootlin.com>
14 I3C busses can be described with a node for the primary I3C controller device
20 pattern: "^i3c@[0-9a-f]+$"
22 "#address-cells":
25 Each I2C device connected to the bus should be described in a subnode.
[all …]
|
| /Documentation/driver-api/ |
| D | dpll.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 PLL - Phase Locked Loop is an electronic circuit which syntonizes clock
11 signal of a device with an external clock signal. Effectively enabling
12 device to run on the same clock signal beat as provided on a PLL input.
14 DPLL - Digital Phase Locked Loop is an integrated circuit which in
29 Device object
32 Single dpll device object means single Digital PLL circuit and bunch of
38 Changing the configuration of dpll device is done with `do` request of
40 A device handle is ``DPLL_A_ID``, it shall be provided to get or set
41 configuration of particular device in the system. It can be obtained
[all …]
|
| D | vfio-mediated-device.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
17 The number of use cases for virtualizing DMA devices that do not have built-in
24 The VFIO driver framework provides unified APIs for direct device access. It is
25 an IOMMU/device-agnostic framework for exposing direct device access to user
26 space in a secure, IOMMU-protected environment. This framework is used for
28 direct device access, virtual machines or user space applications have direct
29 access to the physical device. This framework is reused for mediated devices.
31 The mediated core driver provides a common interface for mediated device
35 * Create and destroy a mediated device
36 * Add a mediated device to and remove it from a mediated bus driver
[all …]
|
| /Documentation/hid/ |
| D | uhid.rst | 2 UHID - User-space I/O driver support for HID subsystem
5 UHID allows user-space to implement HID transport drivers. Please see
6 hid-transport.rst for an introduction into HID transport drivers. This document
9 With UHID, a user-space transport driver can create kernel hid-devices for each
10 device connected to the user-space controlled bus. The UHID API defines the I/O
11 events provided from the kernel to user-space and vice versa.
13 There is an example user-space application in ./samples/uhid/uhid-example.c
16 ------------
18 UHID is accessed through a character misc-device. The minor number is allocated
19 dynamically so you need to rely on udev (or similar) to create the device node.
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
5 controllers. Each pin controller must be represented as a node in device tree,
9 designated client devices. Again, each client device must be represented as a
10 node in device tree, just like any other hardware module.
12 For a client device to operate correctly, certain pin controllers must
15 need to reconfigure pins at run-time, for example to tri-state pins when the
16 device is inactive. Hence, each client device can define a set of named
17 states. The number and names of those states is defined by the client device's
21 for client device device tree nodes to map those state names to the pin
27 in a single place, rather than splitting it across multiple client device
[all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | xlnx,versal-net-cdx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/bus/xlnx,versal-net-cdx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 on run-time.
18 and a unique device ID (for MSI) corresponding to a requestor ID
19 (one to one associated with the device). The streamid and deviceid
20 are used to configure SMMU and GIC-ITS respectively.
22 iommu-map property is used to define the set of stream ids
23 corresponding to each device and the associated IOMMU.
[all …]
|
| /Documentation/devicetree/bindings/slimbus/ |
| D | slimbus.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/slimbus/slimbus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
13 SLIMbus is a 2-wire bus, and is used to communicate with peripheral
14 components like audio-codec.
18 pattern: "^slim(@.*|-([0-9]|[1-9][0-9]+))?$"
20 "#address-cells":
23 "#size-cells":
[all …]
|
12345678910>>...43