Searched full:interpreted (Results 1 – 25 of 89) sorted by relevance
1234
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-dbg-g-chip-info.rst | 94 - Match a chip by this number, interpreted according to the ``type``
98 - Match a chip by this name, interpreted according to the ``type``
|
| D | vidioc-dbg-g-register.rst | 104 - Match a chip by this number, interpreted according to the ``type``
108 - Match a chip by this name, interpreted according to the ``type``
|
| D | planar-apis.rst | 19 Some of the V4L2 API calls and structures are interpreted differently,
|
| D | control.rst | 257 Bits [7:0] of the supplied 32 bit value are interpreted as Blue component,
264 interpreted as Cr component, bits [15:8] as Cb component and bits
281 value is interpreted as bits 0-7 Red color information, bits 8-15
|
| /Documentation/devicetree/bindings/input/ |
| D | input.yaml | 42 Specifies whether the event is to be interpreted as a key, relative,
|
| D | iqs626a.yaml | 496 Specifies whether the event is to be interpreted as a key (1) or
497 a switch (5). By default, Hall-channel events are interpreted as
498 switches and all others are interpreted as keys.
682 must be released in order to be interpreted as a tap.
691 must be completed in order to be interpreted as a flick or swipe.
700 travel in order to be interpreted as a flick or swipe.
|
| D | iqs269a.yaml | 45 interpreted as switch codes. Refer to the datasheet for requirements im-
251 released in order to be interpreted as a tap. Default and maximum values
261 completed in order to be interpreted as a flick or swipe. Default and max-
272 in order to be interpreted as a flick or swipe.
|
| D | adc-joystick.yaml | 78 This property is interpreted as two signed 32 bit values.
|
| D | gpio-keys.yaml | 67 linux,code == axis are released. This value is interpreted
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-gsmi | 32 interpreted by the firmware and may change from
|
| D | sysfs-firmware-dmi-entries | 72 how the rest of the entry should be interpreted.
|
| /Documentation/arch/s390/ |
| D | common_io.rst | 29 give a device number 0xabcd, it will be interpreted as 0.0.abcd.
105 numbers given as 0xabcd will be interpreted as 0.0.abcd.
|
| /Documentation/staging/ |
| D | lzo.rst | 125 encoding will be a copy of 4 or more literal, and must be interpreted
137 following literals for free. It must be interpreted like this :
147 dictionary from a 2..3kB distance, and must be interpreted like this :
|
| /Documentation/driver-api/ |
| D | switchtec.rst | 39 The first 4 bytes will be interpreted as the Command ID and the
|
| /Documentation/virt/kvm/x86/ |
| D | cpuid.rst | 29 be interpreted as if the value was 0x40000001.
|
| /Documentation/admin-guide/ |
| D | efi-stub.rst | 78 because the image we're executing is interpreted by the EFI shell,
|
| /Documentation/devicetree/bindings/phy/ |
| D | samsung,usb3-drd-phy.yaml | 17 PHY id, which is interpreted as follows::
|
| /Documentation/dev-tools/kunit/ |
| D | start.rst | 127 If there is a ``"."`` (period) in the filter, it will be interpreted as a
129 otherwise, it will be interpreted as the name of the test suite.
|
| /Documentation/bpf/ |
| D | map_lpm_trie.rst | 14 ``prefixlen,data`` pairs as its keys. The ``data`` is interpreted in
|
| D | classic_vs_extended.rst | 28 and may let more complex programs to be interpreted.
45 native instruction set and let the rest being interpreted.
|
| /Documentation/input/ |
| D | input-programming.rst | 124 to be interpreted separately, because that'd result in a different movement.
222 KEY_MAX). Value is interpreted as a truth value, i.e. any non-zero value means
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 73 can really be interpreted as any legal argument to
|
| /Documentation/bpf/standardization/ |
| D | instruction-set.rst | 26 "OPTIONAL" in this document are to be interpreted as described in
384 'imm' is interpreted as a 32-bit unsigned value. For ``ALU64``,
386 interpreted as a 64-bit unsigned value.
389 'imm' is interpreted as a 32-bit signed value. For ``ALU64``, 'imm'
391 interpreted as a 64-bit signed value.
|
| /Documentation/filesystems/ |
| D | fuse.rst | 60 which is not interpreted by the kernel.
64 mount system call is interpreted as the name of the device.
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic.txt | 92 should be interpreted the same as for
|
1234