Home
last modified time | relevance | path

Searched +full:use +full:- +full:ram +full:- +full:code (Results 1 – 25 of 104) sorted by relevance

12345

/Documentation/arch/arm/
Dtcm.rst2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
8 This is usually just a few (4-64) KiB of RAM inside the ARM
12 Harvard-architecture, so there is an ITCM (instruction TCM)
24 determine if ITCM (bits 1-0) and/or DTCM (bit 17-16) is present
32 place you put it, it will mask any underlying RAM from the
33 CPU so it is usually wise not to overlap any physical RAM with
47 be able to lock and hide one of the banks for use by the secure
52 - FIQ and other interrupt handlers that need deterministic
55 - Idle loops where all external RAM is set to self-refresh
[all …]
Dporting.rst5 Taken from list archive at http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2001-July/00406…
8 -------------------
14 phys = virt - PAGE_OFFSET + PHYS_OFFSET
18 --------------------
23 the time when you call the decompressor code. You normally call
25 to be located in RAM, it can be in flash or other read-only or
26 read-write addressable medium.
29 Start address of zero-initialised work area for the decompressor.
30 This must be pointing at RAM. The decompressor will zero initialise
43 Physical address to place the initial RAM disk. Only relevant if
[all …]
Dmemory.rst11 free for platforms to use, and which are used by generic code.
18 certain regions of VM space for use for new facilities; therefore
22 Start End Use
24 ffff8000 ffffffff copy_user_page / clear_user_page use.
31 Platforms must not use this address range.
39 in proc-xscale.S to flush the whole data
53 ff800000 ffbfffff Permanent, fixed read-only mapping of the
59 VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space.
68 PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region.
69 This maps the platforms RAM, and typically
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Dnvidia,tegra20-emc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra20-emc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dmitry Osipenko <digetx@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
12 - Thierry Reding <thierry.reding@gmail.com>
15 The External Memory Controller (EMC) interfaces with the off-chip SDRAM to
17 various performance-affecting settings beyond the obvious SDRAM configuration
23 const: nvidia,tegra20-emc
[all …]
/Documentation/admin-guide/
Dramoops.rst9 ------------
11 Ramoops is an oops/panic logger that writes its logs to RAM before the system
13 needs a system with persistent RAM so that the content of that area can
17 ----------------
30 mapping to pgprot_writecombine. Setting ``mem_type=1`` attempts to use
56 to life (i.e. a watchdog triggered). In such cases, RAM may be somewhat
60 ----------------------
64 A. Use the module parameters (which have the names of the variables described
66 boot and then use the reserved memory for ramoops. For example, assuming a
68 the kernel to use only the first 128 MB of memory, and place ECC-protected
[all …]
/Documentation/fb/
Dcirrusfb.rst12 - SD64
13 - Piccolo
14 - Picasso
15 - Spectrum
16 - Alpine (GD-543x/4x)
17 - Picasso4 (GD-5446)
18 - GD-5480
19 - Laguna (GD-546x)
22 - PCI
23 - Zorro
[all …]
Dgxfb.rst11 * No need to use AMD's VSA code (or other VESA emulation layer) in the
16 * Most important: boot logo :-)
23 How to use it?
36 XF68_FBDev should generally work fine, but it is non-accelerated.
48 <x>x<y>[-<bpp>][@<refresh>]
49 vram size of video ram (normally auto-detected)
Dlxfb.rst12 * No need to use AMD's VSA code (or other VESA emulation layer) in the
17 * Most important: boot logo :-)
24 How to use it?
37 XF68_FBDev should generally work fine, but it is non-accelerated.
49 <x>x<y>[-<bpp>][@<refresh>]
50 vram size of video ram (normally auto-detected)
Dintel810.rst20 - Intel 810
21 - Intel 810E
22 - Intel 810-DC100
23 - Intel 815 Internal graphics only, 100Mhz FSB
24 - Intel 815 Internal graphics only
25 - Intel 815 Internal graphics and AGP
30 - Choice of using Discrete Video Timings, VESA Generalized Timing
33 - Supports a variable range of horizontal and vertical resolution and
37 - Supports color depths of 8, 16, 24 and 32 bits per pixel
39 - Supports pseudocolor, directcolor, or truecolor visuals
[all …]
/Documentation/scsi/
DChangeLog.ncr53c8xx1 Sat May 12 12:00 2001 Gerard Roudier (groudier@club-internet.fr)
2 * version ncr53c8xx-3.4.3b
3 - Ensure LEDC bit in GPCNTL is cleared when reading the NVRAM.
4 Fix sent by Stig Telfer <stig@api-networks.com>.
5 - Define scsi_set_pci_device() as nil for kernel < 2.4.4.
7 Mon Feb 12 22:30 2001 Gerard Roudier (groudier@club-internet.fr)
8 * version ncr53c8xx-3.4.3
9 - Call pci_enable_device() as AC wants this to be done.
10 - Get both the BAR cookies actual and PCI BAR values.
12 - Merge changes for linux-2.4 that declare the host template
[all …]
/Documentation/arch/arm/keystone/
Dknav-qmss.rst5 Driver source code path
11 multi-core Navigator. QMSS consist of queue managers, packed-data structure
12 processors(PDSP), linking RAM, descriptor pools and infrastructure
15 management of the packet queues. Packets are queued/de-queued by writing or
18 Linking RAM registers are used to link the descriptors which are stored in
19 descriptor RAM. Descriptor RAM is configurable as internal or external memory.
20 The QMSS driver manages the PDSP setups, linking RAM regions,
29 Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
40 git://git.ti.com/keystone-rtos/qmss-lld.git
43 channels. This firmware is available under ti-keystone folder of
[all …]
/Documentation/arch/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
17 For the purposes of this document, we will use the term `boot loader`
20 hypervisor code, or it may just be a handful of instructions for
26 1. Setup and initialise the RAM
32 1. Setup and initialise RAM
33 ---------------------------
37 The boot loader is expected to find and initialise all RAM that the
38 kernel will use for volatile data storage in the system. It performs
39 this in a machine dependent manner. (It may use internal algorithms
40 to automatically locate and size all RAM, or it may use knowledge of
[all …]
/Documentation/filesystems/
Dramfs-rootfs-initramfs.rst1 .. SPDX-License-Identifier: GPL-2.0
12 --------------
16 RAM-based filesystem.
32 The amount of code required to implement ramfs is tiny, because all the
39 ------------------
41 The older "ram disk" mechanism created a synthetic block device out of
42 an area of RAM and used it as backing store for a filesystem. This block
44 size. Using a ram disk also required unnecessarily copying memory from the
54 since all file access goes through the page and dentry caches. The RAM
57 Another reason ramdisks are semi-obsolete is that the introduction of
[all …]
Dromfs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ROMFS - ROM File System
7 This is a quite dumb, read only filesystem, mainly for initial RAM
17 code). Under the same conditions, the msdos filesystem would need
26 As the name suggests, romfs could be also used (space-efficiently) on
27 various read-only media, like (E)EPROM disks if someone will have the
34 floppy drives can be loaded later if you use the "initrd"--initial
35 RAM disk--feature of the kernel. This would not be really news
43 loaded off the CD at a later stage of the installation. Another use
53 name). The maximum overhead for any non-empty file is the header, and
[all …]
/Documentation/staging/
Dxz.rst1 .. SPDX-License-Identifier: 0BSD
13 for executable code. CRC32 is supported for integrity checking.
17 and information about using the code outside the Linux kernel.
19 For userspace, `XZ Utils`_ provide a zlib-like compression library
20 and a gzip-like command line tool.
28 The xz_dec module provides XZ decompressor with single-call (buffer
29 to buffer) and multi-call (stateful) APIs in include/linux/xz.h.
36 For kernel makefiles, three commands are provided for use with
39 - ``$(call if_changed,xzkern)`` is for compressing the kernel image.
40 It runs the script scripts/xz_wrap.sh which uses arch-optimized
[all …]
/Documentation/admin-guide/pm/
Dsleep-states.rst1 .. SPDX-License-Identifier: GPL-2.0
13 Sleep states are global low-power states of the entire system in which user
14 space code cannot be executed and the overall system activity is significantly
28 Suspend-to-Idle
29 ---------------
31 This is a generic, pure software, light-weight variant of system suspend (also
34 I/O devices into low-power states (possibly lower-power than available in the
38 The system is woken up from this state by in-band interrupts, so theoretically
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
50 -------
[all …]
/Documentation/power/
Duserland-swsusp.rst12 Now, to use the userland interface for software suspend you need special
96 swap files (see Documentation/power/swsusp-and-swap-files.rst for
108 suspend to RAM; using this call causes the kernel to
109 immediately enter the suspend-to-RAM state, so this call must always
111 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
112 is needed to implement the suspend-to-both mechanism in which the
114 to disk, and then the system is suspended to RAM (this makes it possible
115 to resume the system from RAM if there's enough battery power or restore
121 - you cannot read() more than one virtual memory page at a time
122 - read()s across page boundaries are impossible (ie. if you read() 1/2 of
[all …]
/Documentation/devicetree/bindings/sram/
Dsram.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic on-chip SRAM
10 - Rob Herring <robh@kernel.org>
16 child node should use a 'reg' property to specify a specific range of
19 Following the generic-names recommended practice, node names should
30 - mmio-sram
31 - amlogic,meson-gxbb-sram
32 - arm,juno-sram-ns
[all …]
/Documentation/networking/
Dgeneric-hdlc.rst1 .. SPDX-License-Identifier: GPL-2.0
14 - Normal (routed) and Ethernet-bridged (Ethernet device emulation)
16 - ARP support (no InARP support in the kernel - there is an
17 experimental InARP user-space daemon available on:
20 2. raw HDLC - either IP (IPv4) interface or Ethernet device emulation
25 Generic HDLC is a protocol driver only - it needs a low-level driver
28 Ethernet device emulation (using HDLC or Frame-Relay PVC) is compatible
40 gcc -O2 -Wall -o sethdlc sethdlc.c
44 Use sethdlc to set physical interface, clock rate, HDLC mode used,
66 - sets physical interface for a given port
[all …]
/Documentation/arch/x86/
Dintel_txt.rst6 Technology (Intel(R) TXT), defines platform-level enhancements that
9 Intel TXT was formerly known by the code name LaGrande Technology (LT).
13 - Provides dynamic root of trust for measurement (DRTM)
14 - Data protection in case of improper shutdown
15 - Measurement and verification of launched environment
18 non-vPro systems. It is currently available on desktop systems
30 - LinuxTAG 2008:
31 http://www.linuxtag.org/2008/en/conf/events/vp-donnerstag.html
33 - TRUST2008:
34 http://www.trust-conference.eu/downloads/Keynote-Speakers/
[all …]
/Documentation/arch/powerpc/
Dbooting.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
9 bootloader <-> kernel interfaces, in order to avoid the degeneration that had
14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit
15 platforms which move into arch/powerpc will be required to use these rules as
19 of a device-tree whose format is defined after Open Firmware specification.
21 doesn't require the device-tree to represent every device in the system and only
29 code all sorts of tables. It also makes it more flexible for board vendors to do
30 minor hardware upgrades without significantly impacting the kernel code or
47 bindings to powerpc. Only the 32-bit client interface
[all …]
/Documentation/networking/device_drivers/ethernet/toshiba/
Dspider_net.rst1 .. SPDX-License-Identifier: GPL-2.0
29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
31 and is waiting to be emptied and processed by the OS. A "not-in-use"
40 buffers, processing them, and re-marking them empty.
54 descr. The OS will process this descr, and then mark it "not-in-use",
57 all of those behind it should be "not-in-use". When RX traffic is not
62 The head pointer (somewhat mis-named) follows after the tail pointer.
64 a "not-in-use" descr. The OS will perform various housekeeping duties
66 dma-mapping it so as to make it visible to the hardware. The OS will
69 be "not-in-use", and everything behind it should be "empty". If no
[all …]
/Documentation/i2c/
Dsummary.rst6 a protocol developed by Philips. It is a two-wire protocol with variable
10 systems. Some systems use variants that don't meet branding requirements,
14 The latest official I2C specification is the `"I²C-bus specification and user
15 manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_
22 devices connected through SMBus are RAM modules configured using I2C EEPROMs,
26 use its protocols on many I2C systems. However, there are systems that don't
36 .. kernel-figure:: i2c_bus.svg
45 An **algorithm** contains general code that can be used to implement a whole
59 video-related chips.
66 --------
[all …]
/Documentation/admin-guide/mm/
Dzswap.rst10 dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles
11 for potentially reduced swap I/O. This trade-off can also result in a
17 * Desktop/laptop users with limited RAM capacities can mitigate the
24 drastically reducing life-shortening writes.
56 Zswap makes use of zpool for the managing the compressed memory pool. Each
69 means the compression ratio will always be 2:1 or worse (because of half-full
76 with a red-black tree per swap type. The swap offset is the search key for the
79 During a page fault on a PTE that is a swap entry, the swapin code calls the
84 in the swap_map goes to 0) the swap code calls the zswap invalidate function
90 * max_pool_percent - The maximum percentage of memory that the compressed
[all …]
/Documentation/devicetree/bindings/mtd/
Dmtd-physmap.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mtd/mtd-physmap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
10 - Rob Herring <robh@kernel.org>
17 - $ref: mtd.yaml#
18 - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml#
23 - items:
24 - enum:
[all …]

12345