Searched full:identified (Results 1 – 25 of 201) sorted by relevance
123456789
| /Documentation/ABI/testing/ |
| D | procfs-attr-current | 9 of the task identified is LSM dependent.
14 the task identified are LSM dependent.
|
| D | procfs-attr-exec | 10 of the task identified is LSM dependent.
15 the task identified are LSM dependent.
|
| 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 | 16 Users: None identified so far.
40 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
|
| /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
|
| /Documentation/driver-api/media/ |
| 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
|
| /Documentation/iio/ |
| D | iio_dmabuf_api.rst | 39 Attach the DMABUF object, identified by its file descriptor, to the
44 Detach the given DMABUF object, identified by its file descriptor,
|
| /Documentation/usb/ |
| D | functionfs.rst | 43 each FunctionFS instance is identified by the device name used
90 Attach the DMABUF object, identified by its file descriptor, to the
95 Detach the given DMABUF object, identified by its file descriptor,
|
| /Documentation/bpf/ |
| D | map_sk_storage.rst | 72 identified by a `socket` ``fd`` stored in the pointer ``key``. The pointer
96 the socket identified by a `socket` ``fd`` stored in the pointer
108 socket identified by a `socket` ``fd`` stored in the pointer ``key``. Returns
|
| /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 | pv88080.txt | 14 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
|
| /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
|
| D | u-boot.yaml | 28 can be identified by a custom header with magic value.
|
| /Documentation/wmi/devices/ |
| D | wmi-bmof.rst | 23 The Binary MOF WMI device is identified by the WMI GUID ``05901221-D566-11D1-B2F0-00A0C9062910``.
|
| /Documentation/userspace-api/media/dvb/ |
| D | ca-get-slot-info.rst | 34 Returns information about a CA slot identified by
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 13 GPIOs are identified as they are inside the kernel, using integers in
|
| /Documentation/i2c/busses/ |
| D | i2c-ali1535.rst | 30 can be identified by comparing this driver to the i2c-ali15x3 driver. For
|
| /Documentation/networking/devlink/ |
| D | devlink-port.rst | 105 In the above example, the external controller (identified by controller number = 1)
106 doesn't have the eswitch. Local controller (identified by controller number = 0)
148 - Get the MAC address of the VF identified by its unique devlink port index::
155 - Set the MAC address of the VF identified by its unique devlink port index::
164 - Get the MAC address of the SF identified by its unique devlink port index::
171 - Set the MAC address of the SF identified by its unique devlink port index::
|
| /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
|
| /Documentation/filesystems/ |
| D | coda.rst | 528 and Venus will search the directory identified by cfs_lookup_in.VFid.
573 This call returns the attributes of the file identified by fid.
646 Verify if access to the object identified by VFid for
690 The file will be created in the directory identified by VFid, its name
791 identified by destFid with name tname. The source must reside in the
825 directory identified by VFid and named tname. It should point to the
858 identified by VFid.
890 identified by VFid.
923 identified by VFid into the buffer data. The buffer data must be able
957 This request asks Venus to place the file identified by
[all …]
|
123456789