| /linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A 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 …]
|
| /linux/arch/mips/include/asm/octeon/ |
| H A D | cvmx-fau.h | 353 * placed in the scratch memory at byte address scraddr.
361 * Returns Placed in the scratch pad register
373 * placed in the scratch memory at byte address scraddr.
381 * Returns Placed in the scratch pad register
393 * placed in the scratch memory at byte address scraddr.
400 * Returns Placed in the scratch pad register
412 * placed in the scratch memory at byte address scraddr.
418 * Returns Placed in the scratch pad register
441 * Returns Placed in the scratch pad register
464 * Returns Placed in the scratch pad register
[all …]
|
| /linux/Documentation/arch/arm/ |
| H A 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
|
| H A D | memory.rst | 61 be dynamically placed in this region.
78 placed here using dynamic mappings.
86 Per-thread mappings are placed here via
|
| /linux/arch/mips/include/asm/ |
| H A D | pgtable-bits.h | 42 /* Used by TLB hardware (placed in EntryLo*) */
75 /* Used by TLB hardware (placed in EntryLo*) */
112 /* Used by TLB hardware (placed in EntryLo) */
140 /* Used by TLB hardware (placed in EntryLo*) */
172 /* Used by TLB hardware (placed in EntryLo*) */
|
| /linux/Documentation/virt/kvm/x86/ |
| H A 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).
|
| /linux/Documentation/filesystems/spufs/ |
| H A 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
|
| /linux/tools/perf/pmu-events/ |
| H A D | README | 27 should be placed in a separate JSON file - where the file name identifies
37 The JSONs folder for a CPU model/family may be placed in the root arch
38 folder, or may be placed in a vendor sub-folder under the arch folder
|
| /linux/drivers/clk/baikal-t1/ |
| H A D | Kconfig | 10 means of the CCU control registers. These domains and devices placed
23 System Controller. These are five PLLs placed at the root of the
|
| /linux/scripts/ |
| H A D | head-object-list.txt | 3 # The objects listed here are placed at the head of vmlinux. A typical use-case
8 # The code marked as __HEAD goes into the ".head.text" section, which is placed
|
| /linux/drivers/usb/serial/ |
| H A D | io_ti.h | 16 #define DTK_ADDR_SPACE_XDATA 0x03 /* Addr is placed in XDATA space */
17 #define DTK_ADDR_SPACE_I2C_TYPE_II 0x82 /* Addr is placed in I2C area */
18 #define DTK_ADDR_SPACE_I2C_TYPE_III 0x83 /* Addr is placed in I2C area */
|
| /linux/Documentation/driver-api/iio/ |
| H A 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
|
| /linux/drivers/md/ |
| H A D | dm-builtin.c | 5 * The kobject release method must not be placed in the module itself,
18 * If this code were placed in the dm module, the following race may
|
| /linux/drivers/mfd/ |
| H A D | timberdale.h | 84 /* SDHC0 is placed in PCI bar 1 */
88 /* SDHC1 is placed in PCI bar 2 */
|
| /linux/drivers/cpufreq/ |
| H A D | powernow-k8.h | 54 /* writes (wrmsr - opcode 0f 30), the register number is placed in ecx, and */
55 /* the value to write is placed in edx:eax. For reads (rdmsr - opcode 0f 32), */
56 /* the register number is placed in ecx, and the data is returned in edx:eax. */
|
| /linux/Documentation/trace/ |
| H A 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.
|
| /linux/Documentation/devicetree/bindings/powerpc/nintendo/ |
| H A 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.
|
| /linux/Documentation/driver-api/cxl/platform/ |
| H A D | acpi.rst | 64 region is placed in wrong node.
68 * Result: NUMA node being placed in the wrong memory tier.
|
| /linux/Documentation/ABI/testing/ |
| H A 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".
|
| /linux/drivers/acpi/acpica/ |
| H A D | nsxfobj.c | 23 * ret_type - Where the type will be placed
75 * ret_handle - Where the parent handle will be placed in ACPI_EXPORT_SYMBOL()
139 * ret_handle - Where handle to the next object is placed in ACPI_EXPORT_SYMBOL()
|
| /linux/arch/arm64/include/uapi/asm/ |
| H A D | sigcontext.h | 62 * context. Such structures must be placed after the rt_sigframe on the stack
114 * 1) fpsimd_context, esr_context and extra_context must be placed in
115 * sigcontext.__reserved[] if present. They cannot be placed in the
116 * extra space. Any other record can be placed either in the extra
|
| /linux/include/xen/interface/ |
| H A D | features.h | 49 * If set, GNTTABOP_map_grant_ref honors flags to be placed into guest kernel
78 * x86/PVH: If set, ACPI RSDP can be placed at any address. Otherwise RSDP
|
| /linux/tools/perf/tests/shell/common/ |
| H A D | settings.sh | 76 # when $PERFSUITE_RUN_DIR is set to something, all the logs and temp files will be placed there
87 # when $PERFSUITE_RUN_DIR is not set, logs will be placed here
|
| /linux/Documentation/filesystems/ext4/ |
| H A 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
|
| /linux/include/drm/ttm/ |
| H A D | ttm_placement.h | 39 * Buffers placed in TTM_PL_SYSTEM are considered under TTMs control and can
57 * TTM_PL_FLAG_TOPDOWN requests to be placed from the
|