Home
last modified time | relevance | path

Searched +full:device +full:- +full:unique (Results 1 – 25 of 191) sorted by relevance

12345678

/Documentation/userspace-api/media/mediactl/
Dmedia-ioc-g-topology.rst1 .. 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 …]
Dmedia-ioc-device-info.rst1 .. 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/
Domap-keypad.txt1 * 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 …]
Dtwl4030-keypad.txt1 * 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 …]
Dgpio-matrix-keypad.txt1 * 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 …]
Dsamsung-keypad.txt1 * Samsung's Keypad Controller device tree bindings
3 Samsung'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
10 - compatible: should be one of the following
11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad
13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
16 - reg: physical base address of the controller and length of memory mapped
19 - interrupts: The interrupt number to the cpu.
[all …]
Dbrcm,bcm-keypad.txt1 * Broadcom Keypad Controller device tree bindings
3 Broadcom 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 "brcm,bcm-keypad"
17 - reg: physical base address of the controller and length of memory mapped
20 - interrupts: The interrupt number to the cpu.
[all …]
/Documentation/networking/devlink/
Ddevlink-info.rst1 .. 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 …]
Dice.rst1 .. 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 …]
/Documentation/ABI/testing/
Dsysfs-bus-rbd6 (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 …]
Dsysfs-bus-rpmsg4 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 …]
Dsysfs-class-net25 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 …]
Dsysfs-firmware-qemu_fw_cfg7 (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.txt"
30 The only legacy blob displayed is the fw_cfg device revision:
37 displayed as entries named after their unique selector key
49 name The 56-byte nul-terminated ASCII string used as the
64 While the fw_cfg device does not impose any specific naming
72 "etc/boot-fail-wait"
73 "etc/system-states"
[all …]
Dsysfs-class-devfreq-event1 What: /sys/class/devfreq-event/event(x)/
5 Provide a place in sysfs for the devfreq-event objects.
6 This allows accessing various devfreq-event specific variables.
7 The name of devfreq-event object denoted as 'event(x)' which
8 includes the unique number of 'x' for each devfreq-event object.
10 What: /sys/class/devfreq-event/event(x)/name
14 The /sys/class/devfreq-event/event(x)/name attribute contains
15 the name of the devfreq-event object. This attribute is
16 read-only.
18 What: /sys/class/devfreq-event/event(x)/enable_count
[all …]
Dsysfs-devices-platform-ipmi4 Contact: openipmi-developer@lists.sourceforge.net
12 Contact: openipmi-developer@lists.sourceforge.net
23 Contact: openipmi-developer@lists.sourceforge.net
25 (RO) Device revision. Useful for identifying if significant
33 Contact: openipmi-developer@lists.sourceforge.net
35 (RO) Indicates whether device provides device sensor data
42 Contact: openipmi-developer@lists.sourceforge.net
44 (RO) Device id is specified by the manufacturer identified by
46 software to identify the unique application command, OEM
53 Contact: openipmi-developer@lists.sourceforge.net
[all …]
/Documentation/devicetree/bindings/iio/light/
Dsharp,gp2ap002.yaml1 # 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/
Dsummary.rst10 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/
Dipmb.rst15 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 …]
/Documentation/devicetree/bindings/nvmem/
Dzii,rave-sp-eeprom.txt3 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/
Dpci.txt1 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/
Dmsi.txt1 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/driver-api/firmware/
Dbuilt-in-fw.rst2 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.
/Documentation/devicetree/bindings/x86/
Dce4100.txt1 CE4100 Device Tree Bindings
2 ---------------------------
5 format: <vendor>,<chip>-<device>.
11 -------------
14 #address-cells = <1>;
15 #size-cells = <0>;
34 - device_type
35 Device type, must be "cpu".
37 - reg
38 Local APIC ID, the unique number assigned to each processor by
[all …]
/Documentation/s390/
Dpci.rst1 .. SPDX-License-Identifier: GPL-2.0
8 - Pierre Morel
17 -----------------------
28 ---------------
36 - /sys/kernel/debug/s390dbf/pci_msg/sprintf
55 - /sys/bus/pci/slots/XXXXXXXX/power
63 - function_id
66 - function_handle
67 Low-level identifier used for a configured PCI function.
70 - pchid
[all …]
/Documentation/driver-api/rapidio/
Drapidio.rst5 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 ---------------
39 resources such as mailboxes and doorbells. The rio_mport also includes a unique
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
[all …]

12345678