Searched refs:Memory (Results 1 – 25 of 493) sorted by relevance
12345678910>>...20
| /linux-5.19.10/drivers/memory/tegra/ |
| D | Kconfig | 3 bool "NVIDIA Tegra Memory Controller support"
8 This driver supports the Memory Controller (MC) hardware found on
14 tristate "NVIDIA Tegra20 External Memory Controller driver"
21 This driver is for the External Memory Controller (EMC) found on
27 tristate "NVIDIA Tegra30 External Memory Controller driver"
33 This driver is for the External Memory Controller (EMC) found on
39 tristate "NVIDIA Tegra124 External Memory Controller driver"
45 This driver is for the External Memory Controller (EMC) found on
55 tristate "NVIDIA Tegra210 External Memory Controller driver"
59 This driver is for the External Memory Controller (EMC) found on
|
| /linux-5.19.10/drivers/staging/fieldbus/Documentation/ABI/ |
| D | fieldbus-dev-cdev | 6 The cdev interface to drivers for Fieldbus Device Memory
7 (aka. Process Memory).
15 Read from Process Memory's "read area".
19 Write to Process Memory's "write area".
22 When a "Process Memory Read Area Changed" event occurs,
|
| /linux-5.19.10/drivers/misc/cardreader/ |
| D | Kconfig | 10 such as Memory Stick, Memory Stick Pro, Secure Digital and
21 such as Memory Stick, Memory Stick Pro, Secure Digital and
32 such as Memory Stick Pro, Secure Digital and MultiMediaCard.
|
| /linux-5.19.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra20-mc.yaml | 7 title: NVIDIA Tegra20 SoC Memory Controller
15 The Tegra20 Memory Controller merges request streams from various client
17 and returns response data to the various clients. The Memory Controller
21 Tegra20 Memory Controller includes the GART (Graphics Address Relocation
22 Table) which allows Memory Controller to provide a linear view of a
|
| D | nvidia,tegra30-mc.yaml | 7 title: NVIDIA Tegra30 SoC Memory Controller
15 Tegra30 Memory Controller architecturally consists of the following parts:
25 Memory Crossbar, which routes request and responses between Arbitration
27 Memory Crossbar is just a pass through between a single Arbitration Domain
31 are shared across the Memory Subsystem.
33 The Tegra30 Memory Controller handles memory requests from internal clients
78 Memory clock rate in Hz.
|
| /linux-5.19.10/tools/testing/selftests/vm/ |
| D | charge_reserved_hugetlb.sh | 426 echo Memory charged to hugtlb=$hugetlb_difference
427 echo Memory charged to reservation=$reserved_difference
455 echo Memory charged to hugtlb=$hugetlb_difference
456 echo Memory charged to reservation=$reserved_difference
510 echo Memory charged to hugtlb1=$hugetlb_difference1
511 echo Memory charged to reservation1=$reserved_difference1
512 echo Memory charged to hugtlb2=$hugetlb_difference2
513 echo Memory charged to reservation2=$reserved_difference2
556 echo Memory charged to hugtlb1=$hugetlb_difference1
557 echo Memory charged to reservation1=$reserved_difference1
[all …]
|
| /linux-5.19.10/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 3 Contact: Linux Memory Management list <linux-mm@kvack.org>
9 Contact: Linux Memory Management list <linux-mm@kvack.org>
15 Contact: Linux Memory Management list <linux-mm@kvack.org>
21 Contact: Linux Memory Management list <linux-mm@kvack.org>
27 Contact: Linux Memory Management list <linux-mm@kvack.org>
34 Contact: Linux Memory Management list <linux-mm@kvack.org>
42 Contact: Linux Memory Management list <linux-mm@kvack.org>
48 Contact: Linux Memory Management list <linux-mm@kvack.org>
54 Contact: Linux Memory Management list <linux-mm@kvack.org>
61 Contact: Linux Memory Management list <linux-mm@kvack.org>
[all …]
|
| /linux-5.19.10/Documentation/core-api/ |
| D | mm-api.rst | 2 Memory Management APIs
5 User Space Memory Access
19 Memory Allocation Controls
91 Memory pools
103 More Memory Management Functions
|
| D | refcount-vs-atomic.rst | 84 Memory ordering guarantee changes:
97 Memory ordering guarantee changes:
108 Memory ordering guarantee changes:
121 Memory ordering guarantees changes:
137 Memory ordering guarantees changes:
150 Memory ordering guarantees changes:
165 Memory ordering guarantees changes:
|
| /linux-5.19.10/drivers/cxl/ |
| D | Kconfig | 24 Memory (HDM)).
34 bool "RAW Command Interface for Memory Devices"
60 specification, and CXL Fixed Memory Window Structures (CEDT.CFMWS)
64 Memory regions to be managed by LIBNVDIMM.
69 tristate "CXL PMEM: Persistent Memory Support"
82 tristate "CXL: Memory Expansion"
87 RAM" and/or "Persistent Memory" that is fully coherent as if the
89 known as HDM "Host-managed Device Memory".
|
| /linux-5.19.10/drivers/edac/ |
| D | Kconfig | 88 AMD CPUs up to and excluding family 0x17 provide for Memory
104 tristate "Amazon's Annapurna Lab Memory Controller"
193 i7 Core (Nehalem) Integrated Memory Controller that exists on
237 Sandy Bridge, Ivy Bridge and Haswell Integrated Memory Controllers.
247 Skylake server Integrated Memory Controllers. If your
259 10nm server Integrated Memory Controllers. If your
268 Pondicherry2 Integrated Memory Controller. This SoC IP is
278 client SoC Integrated Memory Controller using In-Band ECC IP.
312 tristate "PPC4xx IBM DDR2 Memory Controller"
339 tristate "IBM CPC925 Memory Controller (PPC970FX)"
[all …]
|
| /linux-5.19.10/drivers/memory/samsung/ |
| D | Kconfig | 3 bool "Samsung Exynos Memory Controller support" if COMPILE_TEST
5 Support for the Memory Controller (MC) devices found on
11 tristate "Exynos5422 Dynamic Memory Controller driver"
17 This adds driver for Samsung Exynos5422 SoC DMC (Dynamic Memory
|
| /linux-5.19.10/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 23 READ_AFTER_FREE call trace:|Memory correctly poisoned
25 READ_BUDDY_AFTER_FREE call trace:|Memory correctly poisoned
26 SLAB_INIT_ON_ALLOC Memory appears initialized
27 BUDDY_INIT_ON_ALLOC Memory appears initialized
|
| /linux-5.19.10/Documentation/devicetree/bindings/dma/ |
| D | fsl-imx-sdma.txt | 1 * Freescale Smart Direct Memory Access (SDMA) Controller for i.MX
46 13 Memory Stick Host Controller
47 14 Shared Memory Stick Host Controller
49 16 Memory
50 17 FIFO type Memory
52 19 IPU Memory
|
| /linux-5.19.10/arch/arm/boot/dts/ |
| D | aspeed-bmc-quanta-q71l.dts | 464 /* Memory Riser 1 FRU */
470 /* Memory Riser 2 FRU */
476 /* Memory Riser 3 FRU */
482 /* Memory Riser 4 FRU */
494 /* Memory Riser 5 FRU */
500 /* Memory Riser 6 FRU */
506 /* Memory Riser 7 FRU */
512 /* Memory Riser 8 FRU */
|
| /linux-5.19.10/Documentation/xtensa/ |
| D | atomctl.rst | 12 2. With and without An Intelligent Memory Controller which
19 On the FPGA Cards we typically simulate an Intelligent Memory controller
21 Memory controller we let it to the atomic operations internally while
22 doing a Cached (WB) transaction and use the Memory RCW for un-cached
|
| /linux-5.19.10/Documentation/driver-api/media/ |
| D | v4l2-mem2mem.rst | 3 V4L2 Memory to Memory functions and data structures
|
| /linux-5.19.10/Documentation/gpu/amdgpu/display/ |
| D | dc-glossary.rst | 43 * MCLK: Memory Clock
102 Display Memory Interface
168 Memory Access at Last Level
171 Memory Controller
228 Trusted Memory Zone
|
| /linux-5.19.10/drivers/memory/ |
| D | Kconfig | 3 # Memory devices
7 bool "Memory Controller drivers"
29 This selects the ARM PrimeCell PL172 MultiPort Memory Controller.
86 SoCs. AEMIF stands for Asynchronous External Memory Interface and
111 This driver is for the General Purpose Memory Controller (GPMC)
181 This driver is for the NAND/External Memory Controller (NEMC) in
186 tristate "MediaTek SoC Memory Controller driver" if COMPILE_TEST
189 This driver is for the Memory Controller module in MediaTek SoCs,
197 This driver is for the DDR2/mDDR Memory Controller present on
202 tristate "ARM PL35X Static Memory Controller(SMC) driver"
[all …]
|
| /linux-5.19.10/Documentation/RCU/ |
| D | index.rst | 28 Design/Memory-Ordering/Tree-RCU-Memory-Ordering
|
| /linux-5.19.10/Documentation/PCI/endpoint/ |
| D | pci-ntb-function.rst | 55 5) Memory Window (MW)
154 Memory Window 1 and Doorbell registers are packed together in the
218 Memory Window:
243 BAR4 Memory Window 1
244 BAR5 Memory Window 2
263 BAR2 Doorbell + Memory Window 1
264 BAR3 Memory Window 2
265 BAR4 Memory Window 3
266 BAR5 Memory Window 4
281 | BAR2 | Local Memory | BAR2 |
[all …]
|
| /linux-5.19.10/Documentation/translations/ko_KR/ |
| D | memory-barriers.txt | 147 | CPU 1 |<----->| Memory |<----->| CPU 2 |
235 제공하는데(Memory mapped I/O), 해당 컨트롤 레지스터에 접근하는 순서는 매우
2628 <--- CPU ---> : <----------- Memory ----------->
2632 | CPU | | Memory | : | CPU | | | | |
2634 | | | Queue | : | | | |--->| Memory |
2642 | CPU | | Memory | : | CPU | | |--->| Device |
2699 Memory mapped I/O 는 일반적으로 CPU 의 메모리 공간 내의 한 윈도우의 특정 부분
2884 Chapter 7.1: Memory-Access Ordering
2885 Chapter 7.4: Buffering and Combining Memory Writes
2888 Chapter B2: The AArch64 Application Level Memory Model
[all …]
|
| /linux-5.19.10/Documentation/admin-guide/media/ |
| D | misc-cardlist.rst | 25 vim2m Virtual Memory-to-Memory Driver
|
| /linux-5.19.10/drivers/acpi/numa/ |
| D | Kconfig | 9 bool "ACPI Heterogeneous Memory Attribute Table Support"
15 platform's ACPI HMAT (Heterogeneous Memory Attributes Table),
|
| /linux-5.19.10/drivers/soc/qcom/ |
| D | Kconfig | 81 tristate "Qualcomm On Chip Memory (OCMEM) driver"
85 The On Chip Memory (OCMEM) allocator allows various clients to
141 tristate "Qualcomm Shared Memory Manager (SMEM)"
145 Say y here to enable support for the Qualcomm Shared Memory Manager.
168 tristate "Qualcomm Shared Memory Point to Point support"
174 Say yes here to support the Qualcomm Shared Memory Point to Point
178 tristate "Qualcomm Shared Memory State Machine"
183 Say yes here to support the Qualcomm Shared Memory State Machine.
|
12345678910>>...20