Searched full:placed (Results 1 – 25 of 766) sorted by relevance
12345678910>>...31
| /linux-5.10/drivers/staging/hikey9xx/ |
| D | Kconfig | 3 # to be placed at drivers/phy
14 # to be placed at drivers/spmi
25 # to be placed at drivers/mfd
41 # to be placed at drivers/regulator
|
| /linux-5.10/arch/mips/include/asm/octeon/ |
| 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-5.10/Documentation/virt/kvm/ |
| 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-5.10/Documentation/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 | 56 be dynamically placed in this region.
73 placed here using dynamic mappings.
76 Per-thread mappings are placed here via
|
| /linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | renesas,shdma.txt | 6 SHDMA DT nodes to be placed under a DMA multiplexer node. All such compatible
8 descriptors. Therefore respective DMA DT bindings can also all be placed in the
10 still has to be placed under such a multiplexer node.
|
| /linux-5.10/arch/mips/include/asm/ |
| 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-5.10/Documentation/devicetree/bindings/devfreq/ |
| D | rk3399_dmc.txt | 34 placed into power-down mode if bus is idle
39 placed into self-refresh mode if bus is idle
45 clock gating idle period. Memories are placed
51 period in which memories are placed into
57 memories are placed into self-refresh mode.
|
| /linux-5.10/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
|
| /linux-5.10/drivers/clk/baikal-t1/ |
| 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-5.10/tools/perf/pmu-events/ |
| 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-5.10/Documentation/devicetree/bindings/arm/ |
| D | arm,vexpress-juno.yaml | 92 based systems. Juno r1 also has support for AXI masters placed on
156 compatible is placed directly under this node, sometimes it is placed
159 "simple-bus". If the compatible is placed in the "motherboard" node,
|
| /linux-5.10/arch/arm64/include/uapi/asm/ |
| D | sigcontext.h | 62 * context. Such structures must be placed after the rt_sigframe on the stack
103 * 1) fpsimd_context, esr_context and extra_context must be placed in
104 * sigcontext.__reserved[] if present. They cannot be placed in the
105 * extra space. Any other record can be placed either in the extra
|
| /linux-5.10/crypto/asymmetric_keys/ |
| D | signature.c | 77 * Returns the length of the data placed in the encrypted data buffer or an
98 * Returns the length of the data placed in the decrypted data buffer or an
120 * Returns the length of the data placed in the signature buffer or an error.
|
| /linux-5.10/Documentation/driver-api/iio/ |
| D | buffers.rst | 28 The meta information associated with a channel reading placed in a buffer is
111 Here **scan_index** defines the order in which the enabled channels are placed
112 inside the buffer. Channels with a lower **scan_index** will be placed before
|
| /linux-5.10/drivers/usb/serial/ |
| 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-5.10/arch/arm64/kernel/ |
| D | crash_dump.c | 19 * @buf: buffer where the copied page is placed
57 * @buf: buffer where the data is placed
|
| /linux-5.10/drivers/md/ |
| 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-5.10/Documentation/trace/ |
| D | tracepoints.rst | 16 A tracepoint placed in code provides a hook to call a function (probe)
30 which prototypes are described in a tracepoint declaration placed in a
40 - A tracepoint definition, placed in a header file.
|
| /linux-5.10/Documentation/arm64/ |
| D | booting.rst | 50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
52 using blocks of up to 2 megabytes in size, it must not be placed within
55 NOTE: versions prior to v4.2 also require that the DTB be placed within
134 The Image must be placed text_offset bytes from a 2MB aligned base
142 placed as close as possible to the start of system RAM.
|
| /linux-5.10/drivers/mfd/ |
| D | timberdale.h | 84 /* SDHC0 is placed in PCI bar 1 */
88 /* SDHC1 is placed in PCI bar 2 */
|
| /linux-5.10/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.
|
| /linux-5.10/drivers/cpufreq/ |
| 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-5.10/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".
|
| /linux-5.10/include/xen/interface/ |
| 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
|
12345678910>>...31