Home
last modified time | relevance | path

Searched refs:identified (Results 1 – 25 of 229) sorted by relevance

12345678910

/linux-6.1.9/Documentation/ABI/testing/
Dprocfs-attr-current9 of the task identified is LSM dependent.
14 the task identified are LSM dependent.
Dprocfs-attr-exec10 of the task identified is LSM dependent.
15 the task identified are LSM dependent.
Dsysfs-bus-bcma14 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
Dsysfs-devices-platform-docg316 Users: None identified so far.
40 Users: None identified so far.
Dsysfs-bus-rpmsg7 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
Dsysfs-class-gnss6 The GNSS receiver type. The currently identified types reflect
/linux-6.1.9/Documentation/devicetree/bindings/firmware/
Dcoreboot.txt13 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-6.1.9/Documentation/driver-api/media/
Drc-core.rst55 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-6.1.9/Documentation/devicetree/bindings/regulator/
D88pm860x.txt7 device. Each sub-node is identified using the regulator-compatible
D88pm800.txt7 device. Each sub-node is identified using the node's name (or the deprecated
Disl9305.txt8 device. Each sub-node is identified using the node's name, with valid
Dpv88090.txt8 device. Each sub-node is identified using the node's name, with valid
Dpv88080.txt14 device. Each sub-node is identified using the node's name, with valid
Dmax8907.txt15 device. Each sub-node is identified using the node's name (or the deprecated
/linux-6.1.9/drivers/net/caif/
DKconfig20 identified as N_CAIF. When this ldisc is opened from user space
/linux-6.1.9/Documentation/devicetree/bindings/mtd/partitions/
Dbrcm,bcm963xx-cfe-nor-partitions.txt7 at fixed offsets. A valid firmware partition is identified by the ImageTag
Du-boot.yaml28 can be identified by a custom header with magic value.
/linux-6.1.9/Documentation/userspace-api/media/dvb/
Dca-get-slot-info.rst34 Returns information about a CA slot identified by
/linux-6.1.9/drivers/bcma/
DREADME18 16 devices identified by Broadcom specific fields: manufacturer, id, revision
/linux-6.1.9/Documentation/devicetree/bindings/hwmon/
Dltc2978.txt33 the device. Each sub-node is identified using the node's name, with valid
/linux-6.1.9/Documentation/ABI/obsolete/
Dsysfs-gpio13 GPIOs are identified as they are inside the kernel, using integers in
/linux-6.1.9/arch/m68k/fpsp040/
DREADME28 and that such modified versions are clearly identified as such.
/linux-6.1.9/Documentation/devicetree/bindings/fsi/
Dfsi.txt69 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-6.1.9/Documentation/i2c/busses/
Di2c-ali1535.rst30 can be identified by comparing this driver to the i2c-ali15x3 driver. For
/linux-6.1.9/Documentation/networking/device_drivers/ethernet/intel/
Digbvf.rst63 If an issue is identified with the released source code on a supported kernel

12345678910