Home
last modified time | relevance | path

Searched full:placed (Results 1 – 25 of 1347) sorted by relevance

12345678910>>...54

/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-pylint/
H A D0001-Adjust-test-expectations-for-ptest.patch18 …wrong-import-order:15:0:15:15::"standard import ""datetime"" should be placed before third party i…
19 …wrong-import-order:18:0:18:22::"third party import ""totally_missing"" should be placed before loc…
20 …wrong-import-order:20:0:20:14::"third party import ""astroid"" should be placed before local impor…
21 -wrong-import-order:22:0:22:22::"first party import ""pylint.checkers"" should be placed before loc…
22 -wrong-import-order:23:0:23:25::"first party import ""pylint.config"" should be placed before local…
23 -wrong-import-order:24:0:24:17::"first party import ""pylint.sys"" should be placed before local im…
24 -wrong-import-order:25:0:25:28::"first party import ""pylint.pyreverse"" should be placed before lo…
25 …:0:30:40::"third party import ""six.moves.urllib.parse.quote"" should be placed before first party…
26 -wrong-import-order:31:0:31:23::"first party import ""pylint.constants"" should be placed before lo…
27 -wrong-import-order:32:0:32:19::"standard import ""re"" should be placed before third party imports…
[all …]
/openbmc/u-boot/doc/
H A DREADME.spear36 spear320 build with environment variables placed at default
41 placed in Parallel NOR device
43 spear320 build with environment variables placed in NAND device
46 placed at default location
49 placed in pnor device
51 Build with usbtty terminal as default and environment placed in
/openbmc/linux/Documentation/devicetree/bindings/memory-controllers/
H A Drockchip,rk3399-dmc.yaml61 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 …]
/openbmc/u-boot/include/
H A Dlinker_lists.h39 * This macro declares a variable that is placed into a linker-generated
110 * @_list: Name of the list in which this entry is placed
113 * linker-generated array placed into subsection of .u_boot_list section
135 * @_list: Name of the list in which this entry is placed
139 * a linker-generated array placed into subsection of .u_boot_list
163 * placed into subsection of .u_boot_list section specified by _list
188 * @_list: Name of the list in which this entry is placed
/openbmc/linux/arch/mips/include/asm/octeon/
H A Dcvmx-fau.h353 * 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 …]
/openbmc/u-boot/drivers/block/
H A DKconfig11 A filesystem can be placed in each partition.
28 A filesystem can be placed in each partition.
40 A filesystem can be placed in each partition.
/openbmc/linux/Documentation/arch/arm/
H A Dbooting.rst103 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 Dmemory.rst61 be dynamically placed in this region.
78 placed here using dynamic mappings.
86 Per-thread mappings are placed here via
/openbmc/linux/Documentation/virt/kvm/x86/
H A Dhypercalls.rst13 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).
/openbmc/linux/arch/mips/include/asm/
H A Dpgtable-bits.h42 /* 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*) */
/openbmc/qemu/tests/qemu-iotests/
H A D108173 # reftable was generally placed at the image end (unless something was
176 # This was later changed so the reftable would be placed in the
187 # have then been placed at the end of the image file, but with the new
259 # refblock is placed in the first place possible),
262 # reftable too is placed in the first place possible, but only after
263 # all refblocks have been placed)
266 # if they are placed at the image file's end.
270 # because we expect the reftable to be placed there, and we will have
/openbmc/linux/Documentation/filesystems/spufs/
H A Dspufs.rst90 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
/openbmc/phosphor-debug-collector/
H A Dmeson.options36 description: 'Directory where core dumps are placed',
50 description: 'Directory where bmc dumps are placed',
129 description: 'Directory where fault logs are placed',
/openbmc/u-boot/tools/binman/etype/
H A Dx86_start16_tpl.py19 must be placed at a particular address. This entry holds that code. It is
20 typically placed at offset CONFIG_SYS_X86_START16. The code is responsible
H A Dx86_start16_spl.py19 must be placed at a particular address. This entry holds that code. It is
20 typically placed at offset CONFIG_SYS_X86_START16. The code is responsible
H A Dx86_start16.py19 must be placed at a particular address. This entry holds that code. It is
20 typically placed at offset CONFIG_SYS_X86_START16. The code is responsible
/openbmc/phosphor-logging/
H A Delog_serialize.hpp22 * be placed.
39 * be placed.
/openbmc/u-boot/include/configs/
H A D3c120_devboard.h45 * -The heap is placed below the monitor
46 * -The stack is placed below the heap (&grows down).
H A D10m50_devboard.h45 * -The heap is placed below the monitor
46 * -The stack is placed below the heap (&grows down).
/openbmc/linux/drivers/clk/baikal-t1/
H A DKconfig10 means of the CCU control registers. These domains and devices placed
23 System Controller. These are five PLLs placed at the root of the
/openbmc/linux/tools/perf/pmu-events/
H A DREADME27 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
/openbmc/linux/scripts/
H A Dhead-object-list.txt3 # 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
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Darm,vexpress-juno.yaml92 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,
/openbmc/linux/drivers/usb/serial/
H A Dio_ti.h16 #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 */
/openbmc/linux/crypto/asymmetric_keys/
H A Dsignature.c77 * 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.

12345678910>>...54