Searched refs:identified (Results 1 – 25 of 197) sorted by relevance
12345678
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-bus-bcma | 14 There are a few types of BCMA cores, they can be identified by
30 Each BCMA core is identified by few fields, including class it
|
| D | sysfs-devices-platform-docg3 | 14 Users: None identified so far.
34 Users: None identified so far.
|
| D | sysfs-bus-rpmsg | 7 processor. Channels are identified with a (textual) name,
59 processor. Channels are identified by a textual name (see
83 processor. Channels are identified by a textual name (see
|
| D | sysfs-class-gnss | 6 The GNSS receiver type. The currently identified types reflect
|
| /Linux-v5.4/Documentation/devicetree/bindings/firmware/ |
| D | coreboot.txt | 13 parameters. It is identified by the magic string "LBIO" in its first
20 is identified by a root node descriptor with the magic number
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | rc-core.rst | 55 receivers are identified by ``RC_DRIVER_IR_RAW``, as defined by
58 codes to the Kernel. Such kind of receivers are identified
65 raw TX mode. Such kind of hardware is identified as
|
| /Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | 88pm860x.txt | 7 device. Each sub-node is identified using the regulator-compatible
|
| D | 88pm800.txt | 7 device. Each sub-node is identified using the node's name (or the deprecated
|
| D | isl9305.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| D | pv88090.txt | 8 device. Each sub-node is identified using the node's name, with valid
|
| D | pv88080.txt | 14 device. Each sub-node is identified using the node's name, with valid
|
| D | max8907.txt | 15 device. Each sub-node is identified using the node's name (or the deprecated
|
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | ste-coh901318.txt | 11 COH 901 318 are simple and identified by a single number
|
| /Linux-v5.4/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 7 at fixed offsets. A valid firmware partition is identified by the ImageTag
|
| /Linux-v5.4/Documentation/devicetree/bindings/hwmon/ |
| D | ltc2978.txt | 23 the device. Each sub-node is identified using the node's name, with valid
|
| /Linux-v5.4/drivers/bcma/ |
| D | README | 18 16 devices identified by Broadcom specific fields: manufacturer, id, revision
|
| /Linux-v5.4/Documentation/networking/device_drivers/intel/ |
| D | ice.rst | 44 If an issue is identified with the released source code on a supported kernel
|
| D | igbvf.rst | 63 If an issue is identified with the released source code on a supported kernel
|
| /Linux-v5.4/Documentation/media/uapi/dvb/ |
| D | ca-get-slot-info.rst | 41 Returns information about a CA slot identified by
|
| /Linux-v5.4/Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 13 GPIOs are identified as they are inside the kernel, using integers in
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | README | 28 and that such modified versions are clearly identified as such.
|
| /Linux-v5.4/Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 69 Slaves are identified by a (link-index, slave-id) pair, so require two cells
94 Engines are identified by their address under the slaves' address spaces. We
|
| /Linux-v5.4/drivers/net/caif/ |
| D | Kconfig | 14 identified as N_CAIF. When this ldisc is opened from user space
|
| /Linux-v5.4/Documentation/i2c/busses/ |
| D | i2c-ali1535.rst | 30 can be identified by comparing this driver to the i2c-ali15x3 driver. For
|
| /Linux-v5.4/Documentation/devicetree/bindings/mtd/ |
| D | mtk-quadspi.txt | 31 SPI NOR flash that can be identified by the JEDEC READ ID opcode (0x9F).
|
12345678
