Searched full:placed (Results 1 – 25 of 209) sorted by relevance
123456789
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | rockchip,rk3399-dmc.yaml | 61 memories are placed into power-down mode if bus is idle for PD_IDLE DFI
70 which memories are placed into self-refresh mode if bus is idle for
80 Memories are placed into self-refresh mode and memory controller clock
90 placed into self-refresh power down mode if bus is idle for
99 Defines the standby idle period in which memories are placed into
288 period in which memories are placed into power-down mode if bus is idle
294 period in which memories are placed into self-refresh mode if bus is idle
301 Memories are placed into self-refresh mode and memory controller clock
307 placed into self-refresh power down mode if bus is idle for
312 Defines the standby idle period in which memories are placed into
[all …]
|
| /Documentation/virt/kvm/x86/ |
| D | hypercalls.rst | 13 The hypercall number should be placed in rax and the return value will be
14 placed in rax. No other registers will be clobbered unless explicitly stated
29 Return value is placed in R3.
37 number in $2 (v0). Up to four arguments may be placed in $4-$7 (a0-a3) and
38 the return value is placed in $2 (v0).
|
| /Documentation/arch/arm/ |
| D | booting.rst | 103 Any number of tags can be placed in the list. It is undefined
122 The tagged list must be placed in a region of memory where neither
138 placed in a region of memory where the kernel decompressor will not
152 If an initramfs is in use then, as with the dtb, it must be placed in
174 The zImage may also be placed in system RAM and called there. The
175 kernel should be placed in the first 128MiB of RAM. It is recommended
|
| D | memory.rst | 61 be dynamically placed in this region.
78 placed here using dynamic mappings.
86 Per-thread mappings are placed here via
|
| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 90 When data has been read successfully, four bytes are placed in
109 When data has been read successfully, four bytes are placed in
130 fully, four bytes are placed in the data buffer and the value four is
147 sets errno to EINVAL. Otherwise, a four byte value is placed in
199 sets errno to EINVAL. Otherwise, a four byte value is placed in
220 sets errno to EINVAL. Otherwise, a four byte value is placed in
|
| /Documentation/scheduler/ |
| D | sched-debug.rst | 23 detect if pages are properly placed or if the data should be migrated to a
31 behaviour. If pages are properly placed then the scan delay increases,
|
| /Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | gamecube.txt | 38 The node for the "Flipper" interrupt controller must be placed under
60 The ARAM node must be placed under the DSP node.
|
| /Documentation/driver-api/iio/ |
| D | buffers.rst | 28 The meta information associated with a channel reading placed in a buffer is
113 Here **scan_index** defines the order in which the enabled channels are placed
114 inside the buffer. Channels with a lower **scan_index** will be placed before
|
| /Documentation/devicetree/bindings/input/ |
| D | dlink,dir685-touchkeys.txt | 7 The touchkey device node should be placed inside an I2C bus node.
|
| D | omap-keypad.txt | 5 A key can be placed at each intersection of a unique row and a unique column.
|
| D | twl4030-keypad.txt | 5 A key can be placed at each intersection of a unique row and a unique column.
|
| D | gpio-matrix-keypad.txt | 5 placed at each intersection of a unique row and a unique column. The matrix
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-cciss | 78 Description: Value of "simple" indicates that the controller has been placed
80 controller has been placed in "performant mode".
|
| D | sysfs-bus-iio-cros-ec | 16 the motion sensor is placed. For example, in a laptop a motion
|
| D | sysfs-memory-page-offline | 10 dropping it if possible. The kernel will then be placed
|
| /Documentation/trace/ |
| D | tracepoints.rst | 16 A tracepoint placed in code provides a hook to call a function (probe)
30 whose prototypes are described in a tracepoint declaration placed in a
40 - A tracepoint definition, placed in a header file.
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,vexpress-juno.yaml | 92 based systems. Juno r1 also has support for AXI masters placed on
140 compatible is placed directly under this node, sometimes it is placed
143 "simple-bus". If the compatible is placed in the "motherboard-bus" node,
|
| /Documentation/devicetree/bindings/ptp/ |
| D | ptp-ines.txt | 5 control registers. There can be up to three port handles placed as
|
| /Documentation/filesystems/ext4/ |
| D | blocks.rst | 142 placed within the first 2^32 blocks of a filesystem. Files with extents
143 must be placed within the first 2^48 blocks of a filesystem. It's not
|
| /Documentation/devicetree/bindings/display/ |
| D | dp-aux-bus.yaml | 19 To model this relationship, DP sinks should be placed as children
|
| /Documentation/virt/kvm/loongarch/ |
| D | hypercalls.rst | 8 number is put in a0. Up to five arguments may be placed in registers a1 - a5.
9 The return value is placed in v0 (an alias of a0).
|
| /Documentation/devicetree/bindings/iio/magnetometer/ |
| D | asahi-kasei,ak8974.yaml | 26 interrupt must be placed first. The interrupts can be triggered on
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | qemu,virtual-cpufreq.yaml | 27 performance domains. Regions for each performance domain is placed
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | fsl,qe-firmware.yaml | 18 property, and any firmware-specific properties. The node should be placed
|
| /Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra30-tsensor.yaml | 16 and voltage of the chip. Sensors are placed across the die to gauge the
|
123456789