arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/realtek/rtd1619-mjolnir.dts- Extension
.dts- Size
- 688 bytes
- Lines
- 45
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- Inferred role
- Architecture Layer: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
rtd1619.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
/*
* Copyright (c) 2019 Realtek Semiconductor Corp.
* Copyright (c) 2019 Andreas Färber
*/
/dts-v1/;
#include "rtd1619.dtsi"
/ {
compatible = "realtek,mjolnir", "realtek,rtd1619";
model = "Realtek Mjolnir EVB";
memory@2e000 {
device_type = "memory";
reg = <0x2e000 0x7ffd2000>; /* boot ROM to 2 GiB */
};
chosen {
stdout-path = "serial0:115200n8";
};
aliases {
serial0 = &uart0;
serial1 = &uart1;
serial2 = &uart2;
};
};
/* debug console (J1) */
&uart0 {
status = "okay";
};
/* M.2 slot (CON4) */
&uart1 {
status = "disabled";
};
/* GPIO connector (T1) */
&uart2 {
status = "disabled";
};
Annotation
- Immediate include surface: `rtd1619.dtsi`.
- Atlas domain: Architecture Layer / arch/arm64.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.