Home
last modified time | relevance | path

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

12

/Documentation/devicetree/bindings/misc/
Dnvidia,tegra20-apbmisc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/misc/nvidia,tegra20-apbmisc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
16 - items:
17 - enum:
18 - nvidia,tegra210-apbmisc
19 - nvidia,tegra124-apbmisc
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Dnvidia,tegra30-emc.yaml1 # SPDX-License-Identifier: (GPL-2.0)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra30-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 EMC interfaces with the off-chip SDRAM to service the request stream
16 sent from Memory Controller. The EMC also has various performance-affecting
23 const: nvidia,tegra30-emc
[all …]
Dnvidia,tegra124-emc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra124-emc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
14 The EMC interfaces with the off-chip SDRAM to service the request stream
19 const: nvidia,tegra124-emc
26 - description: external memory clock
28 clock-names:
[all …]
/Documentation/core-api/
Dmemory-hotplug.rst49 struct notifier_block *self, unsigned long action, void *arg);
57 unsigned long start_pfn;
58 unsigned long nr_pages;
63 - start_pfn is start_pfn of online/offline memory.
64 - nr_pages is # of pages of online/offline memory.
65 - status_change_nid_normal is set node id when N_NORMAL_MEMORY of nodemask
66 is (will be) set/clear, if this is -1, then nodemask status is not changed.
67 - status_change_nid is set node id when N_MEMORY of nodemask is (will be)
69 node loses all memory. If this is -1, then nodemask status is not changed.
89 When adding/removing memory that uses memory block devices (i.e. ordinary RAM),
[all …]
Ddma-api.rst8 of the API (and actual examples), see Documentation/core-api/dma-api-howto.rst.
11 Part II describes extensions for supporting non-consistent memory
13 non-consistent platforms (this is usually only legacy platforms) you
16 Part I - dma_API
17 ----------------
19 To get the dma_API, you must #include <linux/dma-mapping.h>. This
27 Part Ia - Using large DMA-coherent buffers
28 ------------------------------------------
76 Part Ib - Using small DMA-coherent buffers
77 ------------------------------------------
[all …]
Ddma-api-howto.rst10 with example pseudo-code. For a concise description of the API, see
11 Documentation/core-api/dma-api.rst.
39 supports 64-bit addresses for main memory and PCI BARs, it may use an IOMMU
40 so devices only need to use 32-bit DMA addresses.
49 +-------+ +------+ +------+
52 C +-------+ --------> B +------+ ----------> +------+ A
54 +-----+ | | | | bridge | | +--------+
55 | | | | +------+ | | | |
56 | CPU | | | | RAM | | | | Device |
58 +-----+ +-------+ +------+ +------+ +--------+
[all …]
/Documentation/admin-guide/pm/
Dsuspend-flows.rst1 .. SPDX-License-Identifier: GPL-2.0
5 System Suspend Code Flows
12 At least one global system-wide transition needs to be carried out for the
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
25 The kernel code flows associated with the suspend and resume transitions for
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
33 boils down to the platform-specific actions carried out by the suspend and
[all …]
/Documentation/mm/
Dhighmem.rst30 +--------+ 0xffffffff
32 +--------+ 0xc0000000
36 +--------+ 0x00000000
39 time, but because we need virtual address space for other things - including
40 temporary maps to access the rest of the physical memory - the actual direct
54 * kmap_local_page(), kmap_local_folio() - These functions are used to create
64 These mappings are thread-local and CPU-local, meaning that the mapping
68 CPU-hotplug until the mapping is disposed.
94 Most code can be designed to use thread local mappings. User should
95 therefore try to design their code to avoid the use of kmap() by mapping
[all …]
/Documentation/arch/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
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
40 to automatically locate and size all RAM, or it may use knowledge of
41 the RAM in the machine, or any other method the boot loader designer
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
[all …]
Dmemory-tagging-extension.rst8 Date: 2020-02-25
18 (Top Byte Ignore) feature and allows software to access a 4-bit
19 allocation tag for each 16-byte granule in the physical address space.
20 Such memory range must be mapped with the Normal-Tagged memory
21 attribute. A logical tag is derived from bits 59-56 of the virtual
34 --------
40 ``PROT_MTE`` - Pages allow access to the MTE allocation tags.
43 user address space and preserved on copy-on-write. ``MAP_SHARED`` is
47 RAM-based file mappings (``tmpfs``, ``memfd``). Passing it to other
48 types of mapping will result in ``-EINVAL`` returned by these system
[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/power/
Dswsusp.rst47 - If you feel ACPI works pretty well on your system, you might try::
51 - If you would like to write hibernation image to swap and then suspend
52 to RAM (provided your platform supports it), you can try::
56 - If you have SATA disks, you'll need recent kernels with SATA suspend
58 are built into kernel -- not modules. [There's way to make
66 before suspend (it is limited to around 2/5 of available RAM by default).
68 - The resume process checks for the presence of the resume device,
72 - The resume process may be triggered in two ways:
81 read-only) otherwise data may be corrupted.
87 Last revised: 2003-10-20 by Pavel Machek
[all …]
Dfreezing-of-tasks.rst11 kernel threads are controlled during hibernation or system-wide suspend (on some
17 There is one per-task flag (PF_NOFREEZE) and three per-task states
23 to system-wide suspend too).
26 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
27 static key freezer_active (as opposed to a per-task flag or state) is used to
45 signal-handling code, but the freezable kernel threads need to call it
61 oom_reaper_list = tsk->oom_reaper_list;
73 entire system-wide transition will be cancelled. For this reason, freezable
84 -------------------------------------------------------------------------
87 - freezes only userspace tasks
[all …]
Druntime_pm.rst5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 put their PM-related work items. It is strongly recommended that pm_wq be
20 them to be synchronized with system-wide power transitions (suspend to RAM,
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
69 dev->driver->pm directly (if present).
73 and bus type. Moreover, the high-priority one will always take precedence over
[all …]
/Documentation/driver-api/
Ddevice-io.rst10 Bus-Independent Device Accesses
27 ----------------------------
35 are starting with one. Physical addresses are of type unsigned long.
49 --------------------
52 memory-mapped registers on the device. Linux provides interfaces to read
53 and write 8-bit, 16-bit, 32-bit and 64-bit quantities. Due to a
54 historical accident, these are named byte, word, long and quad accesses.
82 from config space, which is guaranteed to soft-fail if the card doesn't
94 reg = ha->iobase;
96 WRT_REG_WORD(&reg->ictrl, 0);
[all …]
/Documentation/target/
Dtcmu-design.rst19 2) Writing a user pass-through handler
29 TCM is another name for LIO, an in-kernel iSCSI target (server).
36 modules for file, block device, RAM or using another SCSI device as
38 built-in modules are implemented entirely as kernel code.
41 ----------
47 file, a block device, RAM, or another SCSI device to be used for the
49 these are implemented entirely as kernel code.
52 use case that other non-kernel target solutions, such as tgt, are able
55 in these non-traditional networked storage systems, while still only
63 difficult, because LIO is entirely kernel code. Instead of undertaking
[all …]
/Documentation/virt/kvm/
Dppc-pv.rst1 .. SPDX-License-Identifier: GPL-2.0
8 space code in PR=1 which is user space. This way we trap all privileged
19 The code for that interface can be found in arch/powerpc/kernel/kvm*
35 'hypercall-instructions'. This property contains at most 4 opcodes that make
43 r0 - volatile
44 r3 1st parameter Return code
53 r12 - volatile
56 Hypercall definitions are shared in generic code, so the same hypercall numbers
58 also needs to be ORed with the KVM vendor code which is (42 << 16).
63 Code Meaning
[all …]
/Documentation/admin-guide/mm/
Dmemory-hotplug.rst6 a focus on System RAM, including ZONE_MOVABLE support.
20 - The physical memory available to a machine can be adjusted at runtime, up- or
25 - Replacing hardware, such as DIMMs or whole NUMA nodes, without downtime. One
28 - Reducing energy consumption either by physically unplugging memory modules or
32 used to expose persistent memory, other performance-differentiated memory and
33 reserved memory regions as ordinary system RAM to Linux.
39 ------------------------------
54 ------------------------
71 --------------------------
94 ------------------
[all …]
/Documentation/filesystems/
Dvfs.rst1 .. SPDX-License-Identifier: GPL-2.0
9 - Copyright (C) 1999 Richard Gooch
10 - Copyright (C) 2005 Pekka Enberg
27 ------------------------------
32 cache or dcache). This provides a very fast look-up mechanism to
34 in RAM and are never saved to disc: they exist only for performance.
37 most computers cannot fit all dentries in the RAM at the same time, some
44 ----------------
64 ---------------
67 structure (this is the kernel-side implementation of file descriptors).
[all …]
Dext2.rst1 .. SPDX-License-Identifier: GPL-2.0
18 set using tune2fs(8). Kernel-determined defaults are indicated by (*).
34 errors=remount-ro Remount the filesystem read-only on an error.
40 nouid32 Use 16-bit UIDs and GIDs.
84 ------
93 ------------
110 --------------
140 ------
164 pointers to the next set of blocks), a pointer to a doubly-indirect
166 trebly-indirect block (which contains pointers to doubly-indirect blocks).
[all …]
/Documentation/networking/devlink/
Dice.rst1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
16 * - Name
17 - Mode
18 - Notes
19 * - ``enable_roce``
20 - runtime
21 - mutually exclusive with ``enable_iwarp``
22 * - ``enable_iwarp``
23 - runtime
[all …]
/Documentation/input/devices/
Datarikbd.rst12 provides a convenient connection point for a mouse and switch-type joysticks.
13 The ikbd processor also maintains a time-of-day clock with one second
18 The ikbd communicates with the main processor over a high speed bi-directional
30 ISO key position in the scan code table should exist even if no keyswitch
31 exists in that position on a particular keyboard. The break code for each key
32 is obtained by ORing 0x80 with the make code.
37 Code Command
41 0xF8-0xFB relative mouse position records (lsbs determined by
43 0xFC time-of-day
67 ---------------------------
[all …]
/Documentation/devicetree/
Dusage-model.rst1 .. SPDX-License-Identifier: GPL-2.0
20 so that the operating system doesn't need to hard code details of the
34 maximize use of existing support code, but since property and node
44 ----------
53 the Linux support for those architectures has for a long time used the
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
57 and 64-bit support, the decision was made to require DT support on all
61 blob without requiring a real Open Firmware implementation. U-Boot,
66 existing non-DT aware firmware.
74 -------------
[all …]
/Documentation/driver-api/usb/
Dwriting_musb_glue_layer.rst15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
46 ------------------------
47 | | <------- drivers/usb/gadget
48 | Linux USB Core Stack | <------- drivers/usb/host
49 | | <------- drivers/usb/core
50 ------------------------
[all …]
/Documentation/
Dmemory-barriers.txt19 documentation at tools/memory-model/. Nevertheless, even this memory
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Address-dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]

12