| /linux-6.12.1/include/linux/ |
| D | hp_sdc.h | 2 * HP i8042 System Device Controller -- header
7 * Redistribution and use in source and binary forms, with or without
10 * 1. Redistributions of source code must retain the above copyright
25 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
31 * HP-HIL Technical Reference Manual. Hewlett Packard Product No. 45918A
34 * for Part Number 1820-4784 Revision B. Dwg No. A-1820-4784-2
79 * Nuance: never HP_SDC_ACT_DATAIN | HP_SDC_ACT_DEALLOC, use another
104 #define HP_SDC_STATUS_PUP 0x70 /* Successful power-up self test */
134 #define HP_SDC_STR 0x7f /* i8042 self-test result */
146 #define HP_SDC_CFG_ROLLOVER 0x08 /* WTF is "N-key rollover"? */
[all …]
|
| D | crash_dump.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
12 #define ELFCORE_ADDR_MAX (-1ULL)
13 #define ELFCORE_ADDR_ERR (-2ULL)
34 /* Architecture code defines this if there are other possible ELF
35 * machine types, e.g. on bi-arch capable hardware. */
41 * Architecture code can redefine this if there are any special checks
42 * needed for 32-bit ELF or 64-bit ELF vmcores. In case of 32-bit
73 * This makes use of the fact that due to alignment -2ULL is not
94 * struct vmcore_cb - driver callbacks for /proc/vmcore handling
95 * @pfn_is_ram: check whether a PFN really is RAM and should be accessed when
[all …]
|
| /linux-6.12.1/Documentation/arch/arm/ |
| D | tcm.rst | 2 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 …]
|
| D | porting.rst | 5 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 …]
|
| D | memory.rst | 11 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 …]
|
| /linux-6.12.1/drivers/net/ethernet/amd/ |
| D | mvme147.c | 1 // SPDX-License-Identifier: GPL-2.0-only
6 * Uses the generic 7990.c LANCE code.
30 /* We have 32K of RAM for the init block and buffers. This places
31 * an upper limit on the number of buffers we can use. NetBSD uses 8 Rx
37 #include "7990.h" /* use generic LANCE code */
42 unsigned long ram; member
47 * plus board-specific init, open and close actions.
48 * Oh, and we need to tell the generic code how to read and write LANCE registers...
70 /* Initialise the one and only on-board 7990 */
83 return ERR_PTR(-ENODEV); in mvme147lance_probe()
[all …]
|
| /linux-6.12.1/drivers/block/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
12 drivers. This option alone does not add any kernel code.
25 If you want to use the floppy disk drive(s) of your PC under Linux,
28 <file:Documentation/admin-guide/blockdev/floppy.rst>.
40 If you want to use actual physical floppies and expect to do
41 special low-level hardware accesses to them (access and use
42 non-standard formats, for example), then enable this.
44 Note that the code enabled by this option is rarely used and
64 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
78 This enables support for using Chip RAM and Zorro II RAM as a
[all …]
|
| /linux-6.12.1/arch/riscv/include/asm/ |
| D | xip_fixup.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
12 /* Fix-up address in Flash into address in RAM early during boot before
13 * MMU is up. Because generated code "thinks" data is in Flash, but it
14 * is actually in RAM (actually data is also in Flash, but Flash is
15 * read-only, thus we need to use the data residing in RAM).
17 * The start of data in Flash is _sdata and the start of data in RAM is
18 * CONFIG_PHYS_RAM_BASE. So this fix-up essentially does this:
19 * reg += CONFIG_PHYS_RAM_BASE - _start
27 /* In linker script, at the transition from read-only section to
32 * Consequently, early during boot before MMU is up, the generated code
[all …]
|
| /linux-6.12.1/kernel/power/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 bool "Suspend to RAM and standby"
9 suspend-to-RAM state (e.g. the ACPI S3 state).
12 bool "Enable freezer for suspend to RAM/standby" \
18 done, no tasks are frozen for suspend to RAM/standby.
23 bool "Skip kernel's sys_sync() on suspend to RAM/standby"
30 user-space before invoking suspend. There's a run-time switch
32 This setting changes the default for the run-tim switch. Say Y
54 Alternatively, you can use the additional userland tools available
59 of the reasons to use software suspend is that the firmware hooks
[all …]
|
| /linux-6.12.1/arch/m68k/ |
| D | Kconfig.machine | 1 # SPDX-License-Identifier: GPL-2.0
13 you plan to use this kernel on an Amiga, say Y here and browse the
23 This option enables support for the 68000-based Atari series of
24 computers (including the TT, Falcon and Medusa). If you plan to use
40 computers. If you plan to use this kernel on a Mac, say Y here and
41 browse the documentation available at <http://www.mac.linux-m68k.org/>;
50 Say Y here if you want to run Linux on an MC680x0-based Apollo
70 build a kernel which can run on MVME147 single-board computers. If
105 experimental. If you plan to try to use the kernel on such a machine
130 The Q40 is a Motorola 68040-based successor to the Sinclair QL
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra20-emc.yaml | 1 # 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 …]
|
| /linux-6.12.1/arch/arm/kernel/ |
| D | reboot.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 1996-2000 Russell King - Converted to ARM.
26 * A temporary stack to use for CPU reset. This is static so that we
30 * code.
88 * to execute e.g. a RAM-based pin loop is not sufficient. This allows the
89 * kexec'd kernel to use any and all RAM as it sees fit, without having to
90 * avoid any code or data used by any SW CPU pin loop. The CPU hotplug
111 * Power-off simply requires that the secondary CPUs stop performing any
126 * use soft_restart() as their machine descriptor's .restart hook, since that
129 * This is required so that any code running after reset on the primary CPU
[all …]
|
| /linux-6.12.1/Documentation/scsi/ |
| D | ChangeLog.ncr53c8xx | 1 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 …]
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | ramoops.rst | 9 ------------
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 …]
|
| /linux-6.12.1/arch/x86/kernel/ |
| D | ebda.c | 1 // SPDX-License-Identifier: GPL-2.0
12 * are code), that must not be used by the kernel as available
13 * RAM.
20 * guess the reserved BIOS area by looking at the low BIOS RAM size
26 * - This code also contains a quirk for Dell systems that neglect
27 * to reserve the EBDA area in the 'RAM size' value ...
29 * - The same quirk also avoids a problem with the AMD768MPX
34 * - Plus paravirt systems don't have a reliable value in the
35 * 'BIOS RAM size' pointer we can rely on, so we must quirk
46 * Using memory that is in use by the BIOS or by some DMA device
[all …]
|
| /linux-6.12.1/arch/xtensa/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
61 Xtensa processors are 32-bit RISC machines designed by Tensilica
66 a home page at <http://www.linux-xtensa.org/>.
105 def_bool $(success,test "$(shell,echo __XTENSA_EB__ | $(CC) -E -P -)" = 1)
111 …def_bool $(success,test "$(shell,echo __XTENSA_CALL0_ABI__ | $(CC) -mabi=call0 -E -P - 2>/dev/null…
120 bool "fsf - default (not generic) configuration"
124 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
131 bool "dc233c - Diamond 233L Standard Core Rev.C (LE)"
141 Select this variant to use a custom Xtensa processor configuration.
167 ie: it supports a TLB with auto-loading, page protection.
[all …]
|
| /linux-6.12.1/Documentation/arch/arm/keystone/ |
| D | knav-qmss.rst | 5 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 …]
|
| /linux-6.12.1/drivers/gpu/drm/ |
| D | drm_gem_vram_helper.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 #include <linux/iosys-map.h>
30 * buffer object that is backed by video RAM (VRAM). It can be used for
39 * graphics buffers, such as an on-screen framebuffer. GEM does not provide
42 * contains dedicated video memory, the DRM driver can use the VRAM helper
43 * library. Each active buffer object is stored in video RAM. Active
50 * in &struct drm_device.vram_mm . Use &DRM_GEM_VRAM_DRIVER to initialize
54 * .. code-block:: c
85 * manages an area of video RAM with VRAM MM and provides GEM VRAM objects
90 * clean-up handler to run during the DRM device's release.
[all …]
|
| /linux-6.12.1/Documentation/fb/ |
| D | cirrusfb.rst | 12 - 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 …]
|
| /linux-6.12.1/Documentation/arch/arm64/ |
| D | booting.rst | 13 (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 …]
|
| /linux-6.12.1/arch/powerpc/mm/nohash/ |
| D | tlb_64e.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
7 * Copyright (C) 1995-1996 Gary Thomas (gdt@linuxppc.org)
27 #include <asm/code-patching.h>
32 /* The variables below are currently only used on 64-bit Book3E
45 * do not modify this SPRG in the TLB miss code; for other TLB miss handlers,
56 int tsize = mmu_psize_defs[mmu_pte_psize].shift - 10; in tlb_flush_pgtable()
68 __flush_tlb_page(tlb->mm, start, tsize, 1); in tlb_flush_pgtable()
76 vpte = (vpte >> (PAGE_SHIFT - 3)) & ~0xffful; in tlb_flush_pgtable()
78 __flush_tlb_page(tlb->mm, vpte, tsize, 0); in tlb_flush_pgtable()
102 shift = def->shift; in setup_page_sizes()
[all …]
|
| /linux-6.12.1/drivers/mtd/chips/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "RAM/ROM/Flash chip drivers"
13 support any device that is CFI-compliant, you need to enable this
18 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
22 This option enables JEDEC-style probing of flash chips which are not
23 compatible with the Common Flash Interface, but will use the common
24 CFI-targeted flash drivers for any chips which are identified which
26 covers most AMD/Fujitsu-compatible chips and also non-CFI
39 option does not directly affect the code, but will enable other
53 are expected to be wired to the CPU in 'host-endian' form.
[all …]
|
| /linux-6.12.1/drivers/mtd/ |
| D | Kconfig | 5 Memory Technology Devices are flash, RAM and similar chips, often
24 test. Do not use these tests unless you really know what you do.
44 as block devices, it is possible to use MTD devices which are based
45 on RAM chips in this manner. This block device is a user of MTD
57 You do not need this option for use with the DiskOnChip devices. For
65 This allows you to mount read-only file systems (such as cramfs)
69 You do not need this option for use with the DiskOnChip devices. For
81 is part of the PCMCIA specification. It uses a kind of pseudo-
83 512-byte sectors, on top of which you put a 'normal' file system.
85 You may find that the algorithms used in this code are patented
[all …]
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.rst | 1 .. 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 …]
|
| /linux-6.12.1/drivers/mtd/devices/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
7 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
12 These devices come in memory configurations from 32M - 1G. If you
18 will use a 1G memory map as its view of the device. As a module,
41 tristate "DEC MS02-NV NVRAM module support"
44 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
45 backed-up NVRAM module. The module was originally meant as an NFS
49 If you want to compile this driver as a module ( = code which can be
[all …]
|