Home
last modified time | relevance | path

Searched refs:RAM (Results 1 – 200 of 241) sorted by relevance

12

/linux-4.1.27/drivers/zorro/
Dzorro.ids18 0000 Golem RAM Box 2MB [RAM Expansion]
22 1300 Warp Engine [Accelerator, SCSI Host Adapter and RAM Expansion]
24 0200 Megamix 2000 [RAM Expansion]
36 0a00 A590/A2052/A2058/A2091 [RAM Expansion]
37 2000 A560 [RAM Expansion]
40 5000 A2620 68020 [Accelerator and RAM Expansion]
41 5100 A2630 68030 [Accelerator and RAM Expansion]
51 0200 EXP8000 [RAM Expansion]
64 0100 AX2000 [RAM Expansion]
68 0000 StarBoard II [RAM Expansion]
[all …]
/linux-4.1.27/Documentation/zh_CN/arm/
DBooting40 1、设置和初始化 RAM。
47 1、设置和初始化 RAM
53 引导装载程序应该找到并初始化系统中所有内核用于保持系统变量数据的 RAM。
55 RAM，或可能使用对这个设备已知的 RAM 信息，还可能使用任何引导装载程序
117 标签列表应该保存在系统的 RAM 中。
120 建议放在 RAM 的头 16KiB 中。
126 RAM 中，并用启动数据初始化它。dtb 格式在文档
132 dtb 必须置于内核自解压不会覆盖的内存区。建议将其放置于 RAM 的头 16KiB
146 zImage 也可以被放在系统 RAM（任意位置）中被调用。注意：内核使用映像
147 基地址的前 16KB RAM 空间来保存页表。建议将映像置于 RAM 的 32KB 处。
[all …]
/linux-4.1.27/Documentation/blockdev/
Dramdisk.txt1 Using the RAM disk block device with Linux
9 4) An Example of Creating a Compressed RAM Disk
15 The RAM disk driver is a way to use main system memory as a block device. It
21 The RAM disk dynamically grows as more space is required. It does this by using
22 RAM from the buffer cache. The driver marks the buffers it is using as dirty
25 The RAM disk supports up to 16 RAM disks by default, and can be reconfigured
26 to support an unlimited number of RAM disks (at your own risk). Just change
30 To use RAM disk support with your system, run './MAKEDEV ram' from the /dev
31 directory. RAM disks are all major number 1, and start with minor number 0
34 The new RAM disk also has the ability to load compressed RAM disk images,
[all …]
D00-INDEX18 - short guide on how to set up and use the RAM disk.
Dzram.txt1 zram: Compressed RAM based block devices
6 The zram module creates RAM based block devices named /dev/zram<id>
/linux-4.1.27/Documentation/devicetree/bindings/net/can/
Dm_can.txt7 registers map and Message RAM
18 - bosch,mram-cfg : Message RAM configuration data.
20 RAM and each element(e.g Rx FIFO or Tx Buffer and etc)
21 number in Message RAM is also configurable,
23 private Message RAM are used by this M_CAN controller.
28 The 'offset' is an address offset of the Message RAM
31 RAM. The remain cells are used to specify how many
43 Please refer to 2.4.1 Message RAM Configuration in
/linux-4.1.27/Documentation/zh_CN/arm64/
Dbooting.txt47 1、设置和初始化 RAM
53 1、设置和初始化 RAM
58 引导装载程序应该找到并初始化系统中所有内核用于保持系统变量数据的 RAM。
60 RAM，或可能使用对这个设备已知的 RAM 信息，还可能使用任何引导装载程序
138 x0 = 系统 RAM 中设备树数据块（dtb）的物理地址。
/linux-4.1.27/Documentation/arm/
DPorting21 to be located in RAM, it can be in flash or other read-only or
26 This must be pointing at RAM. The decompressor will zero initialise
39 Physical address to place the initial RAM disk. Only relevant if
44 Virtual address of the initial RAM disk. The following constraint
58 Physical start address of the first bank of RAM.
61 Virtual start address of the first bank of RAM. During the kernel
98 last virtual RAM address (found using variable high_memory).
102 between virtual RAM and the vmalloc area. We do this to allow
110 `pram' specifies the physical start address of RAM. Must always
DBooting17 1. Setup and initialise the RAM.
25 1. Setup and initialise RAM
31 The boot loader is expected to find and initialise all RAM that the
34 to automatically locate and size all RAM, or it may use knowledge of
35 the RAM in the machine, or any other method the boot loader designer
110 The tagged list should be stored in system RAM.
114 it. The recommended placement is in the first 16KiB of RAM.
132 A safe location is just above the 128MiB boundary from start of RAM.
146 be loaded just above the 128MiB boundary from the start of RAM as
160 The zImage may also be placed in system RAM and called there. The
[all …]
Dtcm.txt6 This is usually just a few (4-64) KiB of RAM inside the ARM
30 place you put it, it will mask any underlying RAM from the
31 CPU so it is usually wise not to overlap any physical RAM with
53 - Idle loops where all external RAM is set to self-refresh
54 retention mode, so only on-chip RAM is accessible by
59 the external RAM controller.
70 - Have the remaining TCM RAM added to a special
132 printk("Hello TCM executed from ITCM RAM\n");
Dmemory.txt59 PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region.
60 This maps the platforms RAM, and typically
61 maps all platform RAM in a 1:1 relationship.
DSetup93 be used by loaders if the size of the video RAM can't be obtained
/linux-4.1.27/drivers/block/zram/
DKconfig2 tristate "Compressed RAM block device support"
29 bool "Compressed RAM block device debug support"
34 RAM block device driver.
/linux-4.1.27/drivers/video/console/
DKconfig26 bool "Enable Scrollback Buffer in System RAM"
31 the VGA RAM. The size of this RAM is fixed and is quite small.
33 System RAM which is dynamically allocated during initialization.
34 Placing the scrollback buffer in System RAM will slightly slow
38 RAM to allocate for this buffer. If unsure, say 'N'.
46 Enter the amount of System RAM to allocate for the scrollback
/linux-4.1.27/Documentation/vm/
Dfrontswap.txt3 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
14 a synchronous concurrency-safe page-oriented "pseudo-RAM device" conforming
16 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
17 this pseudo-RAM device is not directly accessible or addressable by the
73 useful for write-balancing for some RAM-like devices). Swap pages (and
74 evicted page-cache pages) are a great use for this kind of slower-than-RAM-
75 but-much-faster-than-disk "pseudo-RAM device" and the frontswap (and
80 provides a huge amount of flexibility for more dynamic, flexible RAM
85 that can be safely kept in RAM. Zcache essentially trades off CPU
93 as in zcache, but then "remotified" to another system's RAM. This
[all …]
Dcleancache.txt103 saved in transcendent memory (RAM that is otherwise not directly
109 fast kernel-directly-addressable RAM and slower DMA/asynchronous devices.
113 balancing for some RAM-like devices). Evicted page-cache pages (and
114 swap pages) are a great use for this kind of slower-than-RAM-but-much-
121 virtual machines. This is really hard to do with RAM and efforts to
125 of flexibility for more dynamic, flexible RAM multiplexing.
127 "fallow" hypervisor-owned RAM to not only be "time-shared" between multiple
129 optimize RAM utilization. And when guest OS's are induced to surrender
130 underutilized RAM (e.g. with "self-ballooning"), page cache pages
137 the proposed "RAMster" driver shares RAM across multiple physical
[all …]
Dzswap.txt5 dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles
16 * Desktop/laptop users with limited RAM capacities can mitigate the
Dovercommit-accounting17 configurable amount (default is 50%) of physical RAM.
Dhighmem.txt144 of RAM into your 32-bit machine. This has a number of consequences:
Dpagemap.txt132 14. SWAPBACKED page is backed by swap/RAM
/linux-4.1.27/arch/m68k/
DKconfig.machine324 comment "RAM configuration"
327 hex "Address of the base of RAM"
330 Define the address that RAM starts at. On many platforms this is
332 platforms choose to setup their RAM at other addresses within the
336 hex "Size of RAM (in bytes), or 0 for automatic"
339 Define the size of the system RAM. If you select 0 then the
340 kernel will try to probe the RAM size at runtime. This is not
348 put at the start of RAM, but it doesn't have to be. On ColdFire
379 of RAM, but usually some small offset from it. Define the start
381 processor vectors at the base of RAM and then the start of the
[all …]
/linux-4.1.27/Documentation/
Dinitrd.txt1 Using the initial RAM disk (initrd)
8 initrd provides the capability to load a RAM disk by the boot loader.
9 This RAM disk can then be mounted as the root file system and programs
27 1) the boot loader loads the kernel and the initial RAM disk
28 2) the kernel converts initrd into a "normal" RAM disk and
58 Loads the specified file as the initial RAM disk. When using LILO, you
59 have to specify the RAM disk image file in /etc/lilo.conf, using the
64 initrd data is preserved but it is not converted to a RAM disk and
77 with the RAM disk mounted as root.
117 Second, the kernel has to be compiled with RAM disk support and with
[all …]
Dramoops.txt10 Ramoops is an oops/panic logger that writes its logs to RAM before the system
12 needs a system with persistent RAM so that the content of that area can
43 to life (i.e. a watchdog triggered). In such cases, RAM may be somewhat
88 You can specify either RAM memory or peripheral devices' memory. However, when
89 specifying RAM, be sure to reserve the memory by issuing memblock_reserve()
105 a stored record from RAM, simply unlink the respective pstore file.
Dbus-virt-phys-mapping.txt19 that is, normal RAM--see later about other details):
128 only talks about "real memory", that is, CPU memory (RAM).
131 memory" on the PCI or ISA bus. That's generally not RAM (although in the case
Dintel_txt.txt127 o As part of its launch, tboot DMA protects all of RAM (using the
162 provides tboot with a set of memory ranges (RAM and RESERVED_KERN
Dgdb-kernel-debugging.txt100 [ 0.000000] e820: BIOS-provided physical RAM map:
Dxz.txt71 megabytes. The decoder needs to have the dictionary in RAM, thus big
DDMA-API-HOWTO.txt54 | CPU | | | | RAM | | | | Device |
59 | | mapping | RAM | by IOMMU
75 memory system maps X to a physical address (Y) in system RAM. The driver
86 RAM.
394 This routine will allocate RAM for that region, so it acts similarly to
Dkernel-parameters.txt104 RAM RAM disk support is enabled.
388 kernel's map of available physical RAM.
515 RAM until it is fully enabled by the userspace
1808 load_ramdisk= [RAM] List of ramdisks to load from floppy
1971 belonging to unused RAM.
2425 noinitrd [RAM] Tells the kernel not to load any configured
2426 initial RAM disk.
2943 prompt_ramdisk= [RAM] List of RAM disks to prompt for floppy disk
2976 ramdisk_blocksize= [RAM]
2979 ramdisk_size= [RAM] Sizes of RAM disks in kilobytes
[all …]
Ddevices.txt105 1 block RAM disk
106 0 = /dev/ram0 First RAM disk
107 1 = /dev/ram1 Second RAM disk
109 250 = /dev/initrd Initial RAM disk
112 /dev/initrd refers to a RAM disk which was preloaded
362 144 = /dev/nvram Non-volatile configuration RAM
785 written data in RAM, as well as writing to flash RAM
1637 90 char Memory Technology Device (RAM, ROM, Flash)
2001 116 block MicroMemory battery backed RAM adapter (NVRAM)
2512 32 = /dev/pcilynx/ram0 RAM space of first PCILynx card
[all …]
D00-INDEX89 - how to use kernel parameters to exclude bad RAM regions.
231 - how to use the RAM disk as an initial/temporary root filesystem.
/linux-4.1.27/arch/arm/mach-shmobile/
Dpm-rcar-gen2.c30 #define RAM 0xe6300000 macro
83 boot_vector_addr = RAM; in rcar_gen2_pm_init()
/linux-4.1.27/Documentation/filesystems/
Dtmpfs.txt14 you gain swapping and limit checking. Another similar thing is the RAM
16 RAM, where you have to create an ordinary filesystem on top. Ramdisks
22 RAM+swap use of a tmpfs instance with df(1) and du(1).
60 default is half of your physical RAM without swap. If you
65 is half of the number of your physical RAM pages, or (on a
66 machine with highmem) the number of lowmem RAM pages,
71 to limit this tmpfs instance to that percentage of your physical RAM:
140 RAM/SWAP in 10240 inodes and it is only accessible by root.
Ddax.txt48 - brd: RAM backed block device driver
83 DAX on a block device that supports DAX, they will still be copied into RAM.
Dromfs.txt3 This is a quite dumb, read only filesystem, mainly for initial RAM
31 RAM disk--feature of the kernel. This would not be really news
168 similarly small writable filesystem for RAM disks.
Dramfs-rootfs-initramfs.txt11 RAM-based filesystem.
37 an area of RAM and used it as backing store for a filesystem. This block
49 since all file access goes through the page and dentry caches. The RAM
/linux-4.1.27/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt6 processors(PDSP), linking RAM, descriptor pools and infrastructure
12 Linking RAM registers are used to link the descriptors which are stored in
13 descriptor RAM. Descriptor RAM is configurable as internal or external memory.
14 The QMSS driver manages the PDSP setups, linking RAM regions,
37 - Queue status RAM.
102 - PDSP internal RAM region.
/linux-4.1.27/Documentation/sound/oss/
DREADME.modules80 DMA buffers for ISA cards on machines with more than 16MB RAM. This is
88 wasteful of RAM, but it guarantees that sound always works.
96 If you have 16MB or less RAM or a PCI sound card, this is wasteful and
97 unnecessary. It is possible that machine with 16MB or less RAM will find
99 cannot find a 64K block free, you will be wasting even more RAM by keeping
101 needed. The proper solution is to upgrade your RAM. But you do also have
DPAS1690 cards on machines with more than 16MB of RAM. This is because ISA
DREADME.OSS454 GUS PnP (with RAM)
543 SoftOSS keeps the samples loaded on the system's RAM so much RAM is
545 of RAM since this is potentially dangerous (you may accidentally run out
1027 GUS PnP (with RAM) is partially supported but it needs to be initialized using
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dcpm.txt34 parameter RAM region (if it has one).
36 * Multi-User RAM (MURAM)
38 The multi-user/dual-ported RAM is expressed as a bus under the CPM node.
Dqe.txt49 * Multi-User RAM (MURAM)
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-etb1020 Description: (RW) Disables write access to the Trace RAM by stopping the
23 into the Trace RAM following the trigger event is equal to the
Dsysfs-bus-coresight-devices-tmc5 Description: (RW) Disables write access to the Trace RAM by stopping the
Dsysfs-class-rc94 suspend to RAM or power off.
109 suspend to RAM or power off.
Dsysfs-firmware-memmap54 - System RAM
Dsysfs-power26 "mem" - "suspend-to-RAM", present if supported.
33 "suspend-to-RAM", "power-on suspend" and "suspend-to-idle" mean.
Dsysfs-devices-power16 RAM) and hibernation (suspend to disk), and to enable or disable
62 transitions (eg. suspend to RAM, hibernation).
/linux-4.1.27/arch/arm/mm/
Dproc-arm740.S77 ldr r0, =(CONFIG_DRAM_BASE & 0xFFFFF000) @ base[31:12] of RAM
78 ldr r3, =(CONFIG_DRAM_SIZE >> 12) @ size of RAM (must be >= 4KB)
85 mcr p15, 0, r0, c6, c1 @ set area 1, RAM
Dproc-arm940.S299 ldr r0, =(CONFIG_DRAM_BASE & 0xFFFFF000) @ base[31:12] of RAM
300 ldr r7, =CONFIG_DRAM_SIZE >> 12 @ size of RAM (must be >= 4KB)
302 mcr p15, 0, r3, c6, c1, 0 @ set area 1, RAM
Dproc-arm946.S345 ldr r0, =(CONFIG_DRAM_BASE & 0xFFFFF000) @ base[31:12] of RAM
346 ldr r7, =CONFIG_DRAM_SIZE @ size of RAM (must be >= 4KB)
Dproc-fa526.S147 mcr p15, 0, r0, c7, c5, 5 @ invalidate IScratchpad RAM
/linux-4.1.27/drivers/mtd/devices/
DKconfig6 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
9 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
124 tristate "Uncached system RAM"
131 tristate "Physical system RAM"
148 tristate "Test driver using RAM"
180 If you have system RAM accessible by the CPU but not used by Linux
182 available RAM starts, and the MTDRAM driver will use it instead of
/linux-4.1.27/Documentation/networking/
Diphase.txt80 The (i)Chip boards have 3 different packet RAM size variants: 128K, 512K and
81 1M. The RAM size decides the number of buffers and buffer size. The default
84 Total Rx RAM Tx RAM Rx Buf Tx Buf Rx buf Tx buf
85 RAM size size size size size cnt cnt
Darcnet-hardware.txt569 | RAM Addr | ___|
595 7-8: RAM Offset Select
637 Setting the Base Memory (RAM) buffer Address
640 The memory buffer requires 2K of a 16K block of RAM. The base of this
646 Switch | Hex RAM | Hex ROM
991 are swapped (S1 is the nodeaddress, S2 sets IO- and RAM-address).
1070 DIP Switches 1-5 of SW2 encode the RAM and ROM Address Range:
1072 Switches RAM ROM
1394 Setting the Base Memory (RAM) buffer Address
1397 The memory buffer (RAM) requires 2K. The base of this buffer can be
[all …]
Dspider_net.txt111 The RX RAM full bug/feature
119 The spidernet chip can save some limited number of these in local RAM.
142 net eth1: Spider RX RAM full, incoming packets might be discarded!
Dcs89x0.txt426 * Chip RAM Test
427 The Chip RAM test insures the 4K of memory internal to the CS8900/20 is
586 * System RAM
/linux-4.1.27/arch/sh/include/mach-ecovec24/mach/
Dpartner-jet-setup.txt5 LIST "zImage (RAM boot)"
6 LIST "This script can be used to boot the kernel from RAM via JTAG:"
/linux-4.1.27/arch/frv/kernel/
Dhead-uc-fr451.S67 # need to tile the remaining IAMPR/DAMPR registers to cover as much of the RAM as possible
87 # GR8 = base of uncovered RAM
88 # GR9 = top of uncovered RAM
Dhead-uc-fr401.S252 # need to tile the remaining IAMPR/DAMPR registers to cover as much of the RAM as possible
269 # GR8 = base of uncovered RAM
270 # GR9 = top of uncovered RAM
Dhead-uc-fr555.S240 # need to tile the remaining IAMPR/DAMPR registers to cover as much of the RAM as possible
257 # GR8 = base of uncovered RAM
258 # GR9 = top of uncovered RAM
Dhead-mmu-fr451.S233 # IAMPR0/DAMPR0 0xC0000000-0xCFFFFFFF Cached kernel RAM Window
251 # need to open a window onto at least part of the RAM for the kernel's use
/linux-4.1.27/Documentation/arm64/
Dbooting.txt24 1. Setup and initialise the RAM
30 1. Setup and initialise RAM
35 The boot loader is expected to find and initialise all RAM that the
38 to automatically locate and size all RAM, or it may use knowledge of
39 the RAM in the machine, or any other method the boot loader designer
113 address near the start of usable system RAM and called there. Memory
115 is strongly recommended that this location is the start of system RAM.
131 x0 = physical address of device tree blob (dtb) in system RAM.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/cpm/
Di2c.txt8 Parameter RAM itself, but the I2C_BASE field of the CPM2 Parameter RAM
/linux-4.1.27/arch/unicore32/configs/
Dunicore32_defconfig8 # Initial RAM filesystem and RAM disk (initramfs/initrd) support
81 # RAM/ROM/Flash chip drivers
/linux-4.1.27/arch/cris/arch-v10/
DREADME.mm41 As a comparison, the Linux/i386 2.0 puts the kernel and physical RAM at
44 map through. That changed in 2.2, putting the kernel/physical RAM at
89 It also means that the total physical RAM that can be mapped is 256 MB
90 (kseg_c above). More RAM can be mapped by choosing a different segmentation
103 chunks of memory not possible using the normal kmalloc physical RAM
129 ( base_c, 0x4 ) | // physical RAM cached area
229 get_vm_area(size). After that, physical RAM pages are allocated and put into
/linux-4.1.27/drivers/block/
DKconfig62 This enables support for using Chip RAM and Zorro II RAM as a
162 tristate "Micro Memory MM5415 Battery Backed RAM support"
166 battery backed (Non-volatile) RAM cards.
360 tristate "RAM block device support"
362 Saying Y here will allow you to use a portion of your RAM memory as
366 store a copy of a minimal root file system off of a floppy into RAM
376 Most normal users won't need the RAM disk functionality, and can
380 int "Default number of RAM disks"
384 The default value is 16 RAM disks. Change this if you know what you
386 in memory, you will need at least one RAM disk (e.g. root on cramfs).
[all …]
/linux-4.1.27/Documentation/x86/x86_64/
Duefi.txt41 physical RAM by using the following kernel command line parameter.
42 add_efi_memmap include EFI memory map of available physical RAM
Dboot-options.txt146 If given as a memory unit, fills all system RAM with nodes of
150 If given as an integer, fills all system RAM with N fake nodes
226 memaper[=<order>] Allocate an own aperture over RAM with size 32MB<<order.
/linux-4.1.27/Documentation/x86/
Dpat.txt30 API | RAM | ACPI,... | Reserved/Holes |
100 Note that this set of APIs only works with IO (non RAM) regions. If driver
101 wants to export a RAM region, it has to do set_memory_uc() or set_memory_wc()
127 Drivers should use set_memory_[uc|wc] to set access type for RAM ranges.
Dmtrr.txt58 This is for video RAM at base address 0xf8000000 and size 4 megabytes. To
/linux-4.1.27/arch/mn10300/mm/
Dcache-inv-by-tag.S151 clr d2 # we're going to clear tag RAM
154 # read the tags from the tag RAM, and if they indicate a valid dirty
159 add d0,a0 # starting dcache tag RAM
Dcache-flush-by-tag.S45 # Flush the entire data cache back to RAM
Dcache-dbg-flush-by-tag.S26 # Flush the entire data cache back to RAM and invalidate the icache
Dcache-dbg-flush-by-reg.S25 # Flush the entire data cache back to RAM and invalidate the icache
DKconfig.cache34 committed to RAM immediately in addition to being stored in the
Dcache-flush-by-reg.S45 # Flush the entire data cache back to RAM
/linux-4.1.27/Documentation/fb/
Dintelfb.txt35 select amount of system RAM in MB to allocate for the video memory
36 if not enough RAM was already allocated by the BIOS.
97 framebuffer will use 8 MB of System RAM. hw acceleration of text and cursor
Dcirrusfb.txt68 CLGEN_USE_HARDCODED_RAM_SETTINGS if you _do_ want to override the RAM
Dvesafb.txt164 remap 'n' MiB of video RAM. If 0 or not specified, remap memory
171 amount of video RAM, use this option to override the BIOS (in MiB).
Duvesafb.txt93 Remap 'n' MiB of video RAM. If 0 or not specified, remap memory
98 amount of video RAM, use this option to override the BIOS (in MiB).
Dintel810.txt82 select amount of system RAM in MB to allocate for the video memory
188 will use 2 MB of System RAM. MTRR support will be enabled. The refresh rate
/linux-4.1.27/arch/arm/mach-realview/
DKconfig122 RealView boards other than PB1176 have the RAM available at
124 the board supports 512MB of RAM, this option allows the
127 RAM to be used with SPARSEMEM.
/linux-4.1.27/fs/pstore/
DKconfig48 tristate "Log panic/oops to a RAM buffer"
57 buffer in RAM where it can be read back at some later point.
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dl2cc.txt36 - arm,data-latency : Cycles of latency for Data RAM accesses. Specifies 3 cells of
39 - arm,tag-latency : Cycles of latency for Tag RAM accesses. Specifies 3 cells of
41 should use 0. Controllers without separate read and write Tag RAM latency
Dvexpress.txt6 peripherals. Processor and RAM "live" on the tiles.
/linux-4.1.27/Documentation/power/
Dstates.txt37 This state can be used for platforms without Power-On Suspend/Suspend-to-RAM
38 support, or it can be used in addition to Suspend-to-RAM (memory sleep)
59 State: Suspend-to-RAM
88 state operates similarly to Suspend-to-RAM, but includes a final step
Ddrivers-testing.txt10 (aka suspend to disk or STD) and suspend to RAM (STR), because each of these
41 f) Attempt to suspend to RAM using the s2ram tool with the driver loaded
Dinterface.txt11 'standby' (Power-On Suspend), 'mem' (Suspend-to-RAM), and 'disk'
60 is set to 2/5 of available RAM by default.
Duserland-swsusp.txt89 SNAPSHOT_S2RAM - suspend to RAM; using this call causes the kernel to
90 immediately enter the suspend-to-RAM state, so this call must always
95 to disk, and then the system is suspended to RAM (this makes it possible
96 to resume the system from RAM if there's enough battery power or restore
D00-INDEX34 - Explains the interaction between Suspend-to-RAM (S3) and CPU hotplug
Dbasic-pm-debugging.txt180 2. Testing suspend to RAM (STR)
207 There is a debugfs entry which shows the suspend to RAM statistics. Here is an
226 Field success means the success number of suspend to RAM, and field fail means
228 to RAM. suspend_stats just lists the last 2 failed devices, error number and
Dcharger-manager.txt5 requires temperature monitoring during suspend-to-RAM state
28 * Support for in suspend-to-RAM polling (with suspend_again callback)
29 While the battery is being charged and the system is in suspend-to-RAM,
Dswsusp.txt37 to RAM (provided your platform supports it), you can try
315 Q: Is there a maximum system RAM size that is supported by swsusp?
325 (over half of the total system RAM), is it correct that it is likely
396 modes like "suspend-to-RAM" or "standby". (Don't write "disk" to the
Dsuspend-and-cpuhotplug.txt6 I. How does the regular CPU hotplug code differ from how the Suspend-to-RAM
16 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
Dfreezing-of-tasks.txt114 memory (approximately 50% of available RAM) and we need to do that before
198 A driver must have all firmwares it may need in RAM before suspend() is called.
/linux-4.1.27/drivers/isdn/hardware/eicon/
Ds_pri.c109 IoAdapter->a.ram_out(&IoAdapter->a, &RAM->SWReg, SWREG_HALT_CPU); in stop_pri_hardware()
111 while ((i < 100) && (IoAdapter->a.ram_in(&IoAdapter->a, &RAM->SWReg) != 0)) in stop_pri_hardware()
Dio.h253 #define RAM ((struct dual *)0) macro
Ddi.c39 #define RAM ((struct dual *)0) macro
/linux-4.1.27/fs/configfs/
DKconfig5 configfs is a RAM-based filesystem that provides the converse
/linux-4.1.27/tools/power/cpupower/
DToDo7 RAM from HW on Intel SandyBridge -> another monitor?
/linux-4.1.27/fs/logfs/
DKconfig11 times and potentially less RAM usage, although the latter has
/linux-4.1.27/Documentation/powerpc/
Dqe_firmware.txt60 The QE architecture allows for only one microcode present in I-RAM for each
66 1) The microcode is placed into I-RAM at a specific location, using the
70 needs split I-RAM. Split I-RAM is only meaningful for SOCs that have
71 QEs with multiple RISC processors, such as the 8360. Splitting the I-RAM
88 being fixed in the RAM package utilizing they should be activated. This data
Dfirmware-assisted-dump.txt49 the low memory (boot memory of size larger of 5% of system RAM
50 or 256MB) of RAM to the previous registered region. It will
56 size will be the larger of 5% of system RAM or 256MB.
65 *not* clear the RAM. It will then launch the bootloader, as
99 then everything but boot memory size of RAM is reserved during
Dbootwrapper.txt60 can be loaded to any location in RAM and jumped to.
68 simpleImage makes is that RAM is correctly initialized
69 and that the MMU is either off or has RAM mapped to
/linux-4.1.27/arch/m68k/hp300/
DREADME.hp3006 Currently only 9000/340 machines have been tested. Any amount of RAM should
/linux-4.1.27/arch/arm/boot/dts/
Dkirkwood-ts219-6281.dts15 /* RAM: 0: 256 MB, 1: 512 MB */
Darmada-xp-matrix.dts61 * This board has 4 GB of RAM, but the last 256 MB of
62 * RAM are not usable due to the overlap with the MBus
Dvexpress-v2p-ca9.dts230 /* PL310, L2 cache, RAM cell supply (not PL310 logic) */
275 /* PL310, L2 cache, RAM cell supply (not PL310 logic) */
289 /* PL310, L2 cache, RAM cell supply (not PL310 logic) */
Dkirkwood-ts219-6282.dts25 /* RAM: 0: 256 MB, 1: 512 MB */
Darmada-xp-gp.dts74 * 8 GB of plug-in RAM modules by default.The amount
/linux-4.1.27/arch/sh/include/mach-kfr2r09/mach/
Dpartner-jet-setup.txt4 LIST "zImage (RAM boot)"
5 LIST "This script can be used to boot the kernel from RAM via JTAG:"
/linux-4.1.27/arch/m68k/kernel/
Dvmlinux-nommu.lds6 * This linker script is equipped to build either ROM loaded or RAM
/linux-4.1.27/Documentation/video4linux/bttv/
DICs20 Winbond W24257AS-35: 32Kx8 CMOS static RAM (Videotext buffer mem)
DCards91 with buffer RAM (e.g. Winbond W24257AS-35: 32Kx8 CMOS static RAM)
/linux-4.1.27/arch/arm/mach-prima2/
Dsleep.S47 @ the RAM is going to self refresh mode
/linux-4.1.27/Documentation/virtual/kvm/
Dmsr.txt19 in guest RAM. This memory is expected to hold a copy of the following
53 guest RAM, plus an enable bit in bit 0. This memory is expected to hold
168 64 byte memory area which must be in guest RAM and must be
204 in guest RAM, plus an enable bit in bit 0. This memory is expected to
239 physical address of a 4 byte memory area which must be in guest RAM and
Dppc-pv.txt180 RAM around where we can live translate instructions to. What happens is the
/linux-4.1.27/kernel/power/
DKconfig2 bool "Suspend to RAM and standby"
8 suspend-to-RAM state (e.g. the ACPI S3 state).
11 bool "Enable freezer for suspend to RAM/standby" \
17 done, no tasks are frozen for suspend to RAM/standby.
46 for suspend states like suspend-to-RAM (STR) often don't work very
/linux-4.1.27/arch/xtensa/kernel/
Dhead.S228 l32i a4, a2, 0 # start destination (in RAM)
229 l32i a5, a2, 4 # end desination (in RAM)
/linux-4.1.27/arch/powerpc/boot/dts/
Dwii.dts20 * contiguous RAM range and will BUG() if the memreserve is outside
23 /*/memreserve/ 0x10000000 0x0004000;*/ /* DSP RAM */
Dmedia5200.dts40 reg = <0x00000000 0x08000000>; // 128MB RAM
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
Dregulator.txt22 - regulator-state-mem sub-root node for Suspend-to-RAM mode
26 : suspend to disk, this state operates similarly to Suspend-to-RAM,
/linux-4.1.27/arch/m68k/q40/
DREADME80 The Q40 consists of a 68040@40 MHz, 1MB video RAM, up to 32MB RAM, AT-style
83 The Q60 has any of 68060 or 68LC060 and up to 128 MB RAM.
/linux-4.1.27/Documentation/frv/
Dbooting.txt29 The kernel will need to be loaded into RAM by RedBoot (or by some alternative
36 RedBoot documentation) and then load it back into RAM. RedBoot keeps
47 default server (as negotiated by BOOTP) and store it into RAM:
/linux-4.1.27/arch/sh/mm/
DKconfig53 does not specify the range that RAM takes.
55 The physical memory (RAM) start address will be automatically
57 boards typically map RAM at 0C000000.
/linux-4.1.27/drivers/net/can/softing/
DKconfig8 Those cards typically use Dual Port RAM to communicate
/linux-4.1.27/arch/frv/
DKconfig.debug14 RAM to avoid excessive linking time. This is only useful for kernel
DKconfig99 with a lot of RAM, this can be wasteful of precious low memory.
/linux-4.1.27/Documentation/devicetree/bindings/net/
Ddavinci_emac.txt24 - ti,davinci-no-bd-ram: boolean, does EMAC have BD RAM?
Dcpsw.txt13 - bd_ram_size : Specifies internal descriptor RAM size
/linux-4.1.27/Documentation/cdrom/
Dpacket-writing.txt65 Packet writing for DVD-RAM media
68 DVD-RAM discs are random writable, so using the pktcdvd driver is not
/linux-4.1.27/arch/arm/mach-sa1100/
DKconfig156 are two different versions CL4 and SL4. CL4 has 32MB RAM and 16MB
157 FLASH. The SL4 version got 64 MB RAM and 32 MB FLASH and a
/linux-4.1.27/drivers/mtd/chips/
DKconfig1 menu "RAM/ROM/Flash chip drivers"
204 tristate "Support for RAM chips in bus mapping"
206 This option enables basic support for RAM chips accessed through
/linux-4.1.27/arch/powerpc/platforms/ps3/
DKconfig142 tristate "PS3 Video RAM Storage Driver"
145 This driver allows you to use excess PS3 video RAM as volatile
/linux-4.1.27/Documentation/scsi/
DChangeLog.ncr53c8xx218 since the chip has on-chip RAM.
388 - Remove all accesses to the on-chip RAM from the C code:
389 Use SCRIPTS to load the on-chip RAM.
393 - The above allows now to use the on-chip RAM without requiring
394 to get access to the on-chip RAM from the C code. This makes
395 on-chip RAM useable for linux-1.2.13 and for Linux-Alpha for
421 64 segments are moved from on-chip RAM scripts.
Ddtc3x80.txt19 between the on-chip buffer and CPU/RAM via memory moves.
Dqlogicfas.txt64 tests, otherwise you will test your RAM and not the files). Then do
/linux-4.1.27/Documentation/i2c/
Dsummary15 devices connected through SMBus are RAM modules configured using I2C EEPROMs,
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dfsl-imx-sdma.txt19 - fsl,sdma-ram-script-name : Should contain the full path of SDMA RAM
/linux-4.1.27/arch/arm/
DKconfig-nommu37 bool 'Install vectors to the beginning of RAM' if DRAM_BASE
DKconfig1657 vmalloc space and actual amount of RAM, you may not need this
1927 directly addressable by the CPU, such as NOR flash. This saves RAM
1929 to RAM. Read-write sections, such as the data section and stack,
1930 are still copied to RAM. The XIP kernel is not compressed since
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt22 No support for suspend/resume to RAM in the current system.
DSuspend.txt120 and the size of memory. For an 64Mbyte RAM area on an 200MHz
DOverview.txt237 Suspend to RAM
240 For boards that provide support for suspend to RAM, the
/linux-4.1.27/drivers/net/wireless/orinoco/
DKconfig49 driver is unloaded. The cache uses 64K of RAM.
129 This is a driver for 802.11b cards using RAM-loadable Symbol
/linux-4.1.27/arch/cris/arch-v32/kernel/
Dhead.S162 ; Check if starting from DRAM (network->RAM boot or unpacked
170 jump _inram ; Jump to cached RAM.
/linux-4.1.27/Documentation/isdn/
DREADME.sc72 configuration. All adapters now use only 16Kbytes of shared RAM
73 versus between 16K and 64K. New methods for using the shared RAM
74 allow us to utilize all of the available RAM on the adapter through
77 have been improved to better detect available shared RAM pages and
DREADME.hysdn127 1002 Boards dual-port RAM test failed
/linux-4.1.27/drivers/mtd/maps/
DKconfig73 and RAM driver code to communicate with chips which are mapped
338 bool "Generic uClinux RAM/ROM filesystem support"
357 tristate "Map driver for platform device RAM (mtd-ram)"
360 Map driver for RAM areas described via the platform device
/linux-4.1.27/Documentation/xtensa/
Dmmu.txt10 0x00000000..0x07FFFFFF (system RAM; this code is actually linked
/linux-4.1.27/Documentation/kdump/
Dkdump.txt257 on the value of System RAM -- that's mostly for distributors that pre-setup
278 1) if the RAM is smaller than 512M, then don't reserve anything
280 2) if the RAM size is between 512M and 2G (exclusive), then reserve 64M
281 3) if the RAM size is larger than 2G, then reserve 128M
384 the physical RAM size exceeds the 4 GB limit and if not, uses ELF32.
/linux-4.1.27/arch/tile/
DKconfig224 bool # "Support for more than 512 MB of RAM"
227 Linux can use the full amount of RAM in the system by
235 machine with more than 512 MB total physical RAM, answer
/linux-4.1.27/arch/microblaze/
DKconfig151 bool "Are you using uncached shadow for RAM ?"
156 The feature requires the design to define the RAM memory controller
/linux-4.1.27/arch/arm/boot/compressed/
Dhead.S689 mov r9, r9, lsl #18 @ start of RAM
690 add r10, r9, #0x10000000 @ a reasonable RAM size
694 1: cmp r1, r9 @ if virt > start of RAM
695 cmphs r10, r1 @ && end of RAM > virt
697 orrlo r1, r1, #0x10 @ Set XN|U for non-RAM
698 orrhs r1, r1, r6 @ set RAM section settings
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/nintendo/
Dgamecube.txt56 1.c.i) The Auxiliary RAM (ARAM) node
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Dmtd-physmap.txt1 CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
/linux-4.1.27/drivers/atm/
Dfirestream.h437 #define RAM 0x1c4 macro
/linux-4.1.27/drivers/net/wireless/hostap/
DKconfig41 volatile memory, i.e. the card RAM. This option is required to
/linux-4.1.27/firmware/
Dwhiteheat_loader.HEX306 * Port 4 LED flashes when the EXTERNAL RAM DOWNLOAD request occurs
Dwhiteheat_loader_debug.HEX395 * Port 4 LED flashes when the EXTERNAL RAM DOWNLOAD request occurs
Dwhiteheat.HEX1089 * Port 4 LED flashes when the EXTERNAL RAM DOWNLOAD request occurs
/linux-4.1.27/Documentation/dvb/
Dbt8xx.txt18 You can save RAM by deselecting every frontend module that your DVB card does not need.
/linux-4.1.27/arch/arm/kernel/
Dhead-nommu.S216 ldr r0, =PLAT_PHYS_OFFSET @ RAM starts at PHYS_OFFSET
/linux-4.1.27/Documentation/devicetree/
Dbooting-without-of.txt71 May 24, 2005: Rev 0.3 - Precise that DT block has to be in RAM
171 r2 : Physical address of tagged list in system RAM
185 (defined in chapter II) in RAM. Device tree can be located
186 anywhere in system RAM, but it should be aligned on a 64 bit
233 (defined in chapter II) in RAM
308 II) in RAM. The device tree can be located anywhere in the first
336 the block to RAM before passing it to the kernel.
948 earlier, a 970 based machine with 6Gb of RAM could typically
1368 RAM, or even placed outside of kernel RAM. For example, the Keystone 2 SoC
1370 - RAM range: [0x8 0000 0000, 0x8 FFFF FFFF]
[all …]
/linux-4.1.27/Documentation/misc-devices/
Dspear-pcie-gadget.txt67 to the PCIe host, then host sees this device as 1MB RAM.
/linux-4.1.27/arch/mn10300/
DKconfig.debug42 RAM to avoid excessive linking time. This is only useful for kernel
DKconfig150 hex "Base address of kernel RAM"
/linux-4.1.27/Documentation/trace/
Dcoresight.txt222 RAM read ptr: 0x0
223 RAM wrt ptr: 0x19d3 <----- The write pointer is moving
/linux-4.1.27/Documentation/video4linux/
Dpxa_camera.txt87 The DMA chain starts transferring data into videobuffer RAM pages.
/linux-4.1.27/drivers/mtd/
DKconfig5 Memory Technology Devices are flash, RAM and similar chips, often
173 on RAM chips in this manner. This block device is a user of MTD
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Dtrivial-devices.txt42 dallas,ds1338 I2C RTC with 56-Byte NV RAM
/linux-4.1.27/arch/xtensa/
DKconfig218 Linux can use the full amount of RAM in the system by
228 machine with more than 128 MB total physical RAM, answer
/linux-4.1.27/mm/
DKconfig558 compress them into a dynamically allocated RAM-based memory pool.
560 in the case where decompressing from RAM is faster that swap device
592 compressed RAM pages. zsmalloc uses virtual memory mapping
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic79xx.reg1570 * SCSI RAM BIST0
1599 * SCSI RAM BIST 1
2932 * CMC SCB RAM Address Pointer
2998 * CMC SG RAM Data Port
3008 * CMC SCB RAM Data Port
3414 * Instruction RAM Diagnostics
3454 * Sequencer RAM Data Port
3669 /* ---------------------- Scratch RAM Offsets ------------------------- */
Daic7xxx.reg622 * Sequencer RAM Data (p. 3-34)
756 field INTSCBRAMSEL 0x08 /* Internal SCB RAM Select */
757 field RAMPS 0x04 /* External SCB RAM Present */
1381 /* ---------------------- Scratch RAM Offsets ------------------------- */
/linux-4.1.27/Documentation/cris/
DREADME81 ROM fs in RAM, size 1376256 bytes
/linux-4.1.27/Documentation/target/
Dtcmu-design.txt31 modules for file, block device, RAM or using another SCSI device as
41 file, a block device, RAM, or another SCSI device to be used for the
/linux-4.1.27/arch/cris/arch-v10/drivers/
DKconfig469 bool "I2C EEPROM (non-volatile RAM) support"
472 Enables I2C EEPROM (non-volatile RAM) on PB0 and PB1 using the I2C
/linux-4.1.27/arch/metag/
DKconfig89 vmalloc space and actual amount of RAM, you may not need this
/linux-4.1.27/Documentation/devicetree/bindings/memory-controllers/
Dti-aemif.txt7 per chip select. Synchronous memories such as DDR1 SD RAM, SDR SDRAM
/linux-4.1.27/Documentation/hwmon/
Df71805f21 test system (custom Jetway K8M8MS motherboard, with CPU and RAM) and
/linux-4.1.27/Documentation/input/
Diforce-protocol.txt228 The amount of RAM may vary, I encountered values from 200 to 1000 bytes. Below
/linux-4.1.27/arch/parisc/
DKconfig198 At the moment, only people willing to use more than 2GB of RAM,
/linux-4.1.27/Documentation/dmaengine/
Dprovider.txt37 Moreover, some DMA controllers, whenever the RAM is used as a source
230 Addresses pointing to RAM are typically incremented (or decremented)
/linux-4.1.27/init/
DKconfig155 will need at least 8MB RAM or more for booting.
218 used to provide more virtual memory than the actual RAM present
1279 bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
1282 The initial RAM filesystem is a ramfs which is loaded by the
1288 If RAM disk support (BLK_DEV_RAM) is also included, this
1289 also enables initial RAM disk (initrd) support and adds
/linux-4.1.27/arch/m32r/
DKconfig217 bool "Internal RAM Support"
/linux-4.1.27/Documentation/watchdog/
Dwatchdog-api.txt24 the system. If userspace fails (RAM error, kernel bug, whatever), the
/linux-4.1.27/arch/x86/
DKconfig1190 more than 1 Gigabyte total physical RAM, answer "off" here (default
1197 If the machine has between 1 and 4 Gigabytes physical RAM, then
1219 gigabytes of physical RAM.
1227 gigabytes of physical RAM.
1440 For systems with a lot of RAM, this can be wasteful of precious
1484 By default we reserve the first 64K of physical RAM, as a
2136 all but the first 4 MB of RAM)
2140 9) install a fan for the video card or exchange video RAM
2142 11) exchange RAM chips
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt882 a part (1/8th) of the available RAM pages.
890 The value written is checked against the available RAM pages. If the
892 available RAM pages threads-max is reduced accordingly.
/linux-4.1.27/Documentation/usb/
Dpersist.txt54 suspend-to-RAM. On almost all systems, no suspend current is
/linux-4.1.27/Documentation/arm/SA1100/
DAssabet87 First, the kernel image must be loaded into RAM. If you have the zImage file
/linux-4.1.27/sound/oss/
DKconfig264 cards on machines with more than 16MB of RAM. This is because ISA
274 Say Y unless you have 16MB or more RAM or a PCI sound card.
/linux-4.1.27/arch/blackfin/
DKconfig403 hex "Physical RAM Base"
972 bool "RAM"
974 The kernel will be resident in RAM when running.
/linux-4.1.27/drivers/media/usb/pwc/
Dphilips.txt76 up 460 KB of RAM, so unless you have a lot of memory setting this to
/linux-4.1.27/drivers/macintosh/
DKconfig86 RAM and the RTC (real time clock) chip. Say Y to enable support for
/linux-4.1.27/arch/powerpc/platforms/
DKconfig.cputype238 If you have more than 3.5GB of RAM or so, you also need to enable
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-cd.1994-2004193 * - Detect DVD-ROM/RAM drives
/linux-4.1.27/drivers/power/
DKconfig345 runtime and in suspend-to-RAM by waking up the system periodically
/linux-4.1.27/Documentation/PCI/
Dpci.txt332 on systems where System RAM exists above 4G _physical_ address.
338 can directly address "consistent memory" in System RAM above 4G physical

12