Searched +full:device +full:- +full:unique (Results 1 – 25 of 242) sorted by relevance
12345678910
| /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 …]
|
| D | media-ioc-device-info.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 MEDIA_IOC_DEVICE_INFO - Query device information
35 query device information, applications call the ioctl with a pointer to
44 .. flat-table:: struct media_device_info
45 :header-rows: 0
46 :stub-columns: 0
49 * - char
50 - ``driver``\ [16]
51 - Name of the driver implementing the media API as a NUL-terminated
59 * - char
[all …]
|
| /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 …]
|
| D | twl4030-keypad.txt | 1 * TWL4030's Keypad Controller device tree bindings
3 TWL4030'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,twl4030-keypad": For controllers compatible with twl4030 keypad
18 - interrupt: should be one of the following
[all …]
|
| D | gpio-matrix-keypad.txt | 1 * GPIO driven matrix keypad device tree bindings
5 placed at each intersection of a unique row and a unique column. The matrix
6 keypad can sense a key-press and key-release by means of GPIO lines and
10 - compatible: Should be "gpio-matrix-keypad"
11 - row-gpios: List of gpios used as row lines. The gpio specifier
14 - col-gpios: List of gpios used as column lines. The gpio specifier
17 - linux,keymap: The definition can be found at
18 bindings/input/matrix-keymap.txt
21 - linux,no-autorepeat: do no enable autorepeat feature.
22 - wakeup-source: use any event on keypad as wakeup event.
[all …]
|
| D | mediatek,mt6779-keypad.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/mediatek,mt6779-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mattijs Korpershoek <mkorpershoek@baylibre.com>
13 - $ref: /schemas/input/matrix-keymap.yaml#
16 Mediatek's Keypad controller is used to interface a SoC with a matrix-type
17 keypad device. The keypad controller supports multiple row and column lines.
18 A key can be placed at each intersection of a unique row and a unique column.
19 The keypad controller can sense a key-press and key-release and report the
[all …]
|
| D | samsung,s3c6410-keypad.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/input/samsung,s3c6410-keypad.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 Samsung SoC Keypad controller is used to interface a SoC with a matrix-type
11 keypad device. The keypad controller supports multiple row and column lines.
12 A key can be placed at each intersection of a unique row and a unique column.
13 The keypad controller can sense a key-press and key-release and report the
17 - Krzysztof Kozlowski <krzk@kernel.org>
22 - samsung,s3c6410-keypad
[all …]
|
| /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 …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-vfio-dev | 1 What: /sys/.../<device>/vfio-dev/vfioX/
5 This directory is created when the device is bound to a
7 exists for a standard 'struct device'. 'X' is a unique
8 index marking this device in vfio.
|
| 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 …]
|
| D | sysfs-bus-rpmsg | 4 Contact: Ohad Ben-Cohen <ohad@wizery.com>
6 Every rpmsg device is a communication channel with a remote
16 Contact: Ohad Ben-Cohen <ohad@wizery.com>
18 Every rpmsg device is a communication channel with a remote
22 a unique rpmsg address (a 32 bits integer). This way when
34 Contact: Ohad Ben-Cohen <ohad@wizery.com>
36 Every rpmsg device is a communication channel with a remote
40 a unique rpmsg address (a 32 bits integer). This way when
56 Contact: Ohad Ben-Cohen <ohad@wizery.com>
58 Every rpmsg device is a communication channel with a remote
[all …]
|
| D | sysfs-class-net-peak_usb | 5 Contact: Stephane Grosjean <s.grosjean@peak-system.com>
7 PEAK PCAN-USB devices support user-configurable CAN channel
10 if a USB device exports multiple CAN interfaces, each of them
11 can be assigned a unique channel ID.
12 This attribute provides read-only access to the currently
14 device type, the identifier has a length of 8 or 32 bit. The
16 hexadecimal value in big endian format. If the device only
|
| D | sysfs-class-net | 25 2 stolen from another device
35 Values vary based on the lower-level protocol used by the
54 01-80-C2-00-00-0X on a bridge device. Only values that set bits
62 0 01-80-C2-00-00-00 Bridge Group Address used for STP
63 1 01-80-C2-00-00-01 (MAC Control) 802.3 used for MAC PAUSE
64 2 01-80-C2-00-00-02 (Link Aggregation) 802.3ad
68 care when forwarding control frames e.g. 802.1X-PAE or LLDP.
101 Indicates the device unique identifier. Format is an hexadecimal
104 address as their parent device.
111 Indicates the port number of this network device, formatted
[all …]
|
| D | sysfs-firmware-qemu_fw_cfg | 7 (fw_cfg) device, originally intended as a way for the host to
11 useful as an out-of-band, asynchronous mechanism for providing
14 The authoritative guest-side hardware interface documentation
15 to the fw_cfg device can be found in "docs/specs/fw_cfg.rst"
17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
31 The only legacy blob displayed is the fw_cfg device revision:
38 displayed as entries named after their unique selector key
50 name The 56-byte nul-terminated ASCII string used as the
65 While the fw_cfg device does not impose any specific naming
73 "etc/boot-fail-wait"
[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.
17 All devices on the CDX bus will have a unique streamid (for IOMMU)
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
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | audio-graph.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/audio-graph.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
13 - $ref: /schemas/sound/dai-params.yaml#
17 $ref: /schemas/types.yaml#/definitions/phandle-array
21 description: device name prefix
28 $ref: /schemas/types.yaml#/definitions/non-unique-string-array
35 $ref: /schemas/types.yaml#/definitions/non-unique-string-array
[all …]
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | sharp,gp2ap002.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
20 - sharp,gp2ap002a00f
21 - sharp,gp2ap002s00f
30 vdd-supply:
33 vio-supply:
36 io-channels:
40 io-channel-names:
[all …]
|
| /Documentation/driver-api/soundwire/ |
| D | summary.rst | 10 SoundWire is a 2-pin multi-drop interface with data and clock line. It
15 commands over a single two-pin interface.
23 (4) Device status monitoring, including interrupt-style alerts to the Master.
38 +---------------+ +---------------+
40 | Master |-------+-------------------------------| Slave |
42 | |-------|-------+-----------------------| |
43 +---------------+ | | +---------------+
47 +--+-------+--+
52 +-------------+
58 The MIPI SoundWire specification uses the term 'device' to refer to a Master
[all …]
|
| /Documentation/driver-api/ |
| D | ipmb.rst | 15 hot-swapping disk drivers in the system chassis, etc...
19 sends IPMI requests to a device (usually a Satellite Management
20 Controller or Satellite MC) via IPMB and the device
27 ----------------------------
29 ipmb-dev-int - This is the driver needed on a Satellite MC to
43 --------------------
53 Device (SMB0) // Example SMBus host controller
55 Name (_HID, "<Vendor-Specific HID>") // Vendor-Specific HID
56 Name (_UID, 0) // Unique ID of particular host controller
59 Device (IPMB)
[all …]
|
| 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 …]
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | zii,rave-sp-eeprom.txt | 3 RAVE SP EEPROM device is a "MFD cell" device exposing physical EEPROM
4 attached to RAVE Supervisory Processor. It is expected that its Device
6 parent RAVE SP device (as documented in
7 Documentation/devicetree/bindings/mfd/zii,rave-sp.txt)
11 - compatible: Should be "zii,rave-sp-eeprom"
15 - zii,eeprom-name: Unique EEPROM identifier describing its function in the
25 rave-sp {
26 compatible = "zii,rave-sp-rdu1";
27 current-speed = <38400>;
30 compatible = "zii,rave-sp-eeprom";
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 1 PCI bus bridges have standardized Device Tree bindings:
3 PCI Bus Binding to: IEEE Std 1275-1994
4 https://www.devicetree.org/open-firmware/bindings/pci/pci2_1.pdf
9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
14 - linux,pci-domain:
16 otherwise an unstable (across boots) unique number will be assigned.
20 number for each host bridge in the system must be unique.
21 - max-link-speed:
27 - reset-gpios:
30 - supports-clkreq:
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 1 This document describes the generic device tree binding for MSI controllers and
14 - The doorbell (the MMIO address written to).
19 - The payload (the value written to the doorbell).
24 - Sideband information accompanying the write.
28 MSI controller and device rather than a property of either in isolation).
38 --------------------
40 - msi-controller: Identifies the node as an MSI controller.
43 --------------------
45 - #msi-cells: The number of cells in an msi-specifier, required if not zero.
50 The meaning of the msi-specifier is defined by the device tree binding of
[all …]
|
| /Documentation/gpu/ |
| D | drm-usage-stats.rst | 1 .. _drm-client-usage-stats:
8 `fops->show_fdinfo()` as part of the driver specific file operations registered
22 - File shall contain one key value pair per one line of text.
23 - Colon character (`:`) must be used to delimit keys and values.
24 - All keys shall be prefixed with `drm-`.
25 - Whitespace between the delimiter and first non-whitespace character shall be
27 - Keys are not allowed to contain whitespace characters.
28 - Numerical key value pairs can end with optional unit string.
29 - Data type of the value is fixed as defined in the specification.
32 ---------
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 2 Built-in firmware
5 Firmware can be built-in to the kernel, this means building the firmware
8 directly. You can enable built-in firmware using the kernel configuration
18 * Firmware is needed for accessing the boot device, and the user doesn't
22 able to make use of built-in firmware:
24 * Legalese - firmware is non-GPL compatible
28 * Some firmware files may be really large in size. The remote-proc subsystem
30 * The firmware may need to be scraped out from some device specific location
32 calibration data can be unique per sold device.
|
12345678910