arch/arm64/boot/dts/amlogic/amlogic-t7-a311d2-an400.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/amlogic/amlogic-t7-a311d2-an400.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/amlogic/amlogic-t7-a311d2-an400.dts- Extension
.dts- Size
- 770 bytes
- Lines
- 40
- 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
amlogic-t7.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 MIT)
/*
* Copyright (c) 2023 Amlogic, Inc. All rights reserved.
*/
/dts-v1/;
#include "amlogic-t7.dtsi"
/ {
model = "Amlogic A311D2 AN400 Development Board";
compatible = "amlogic,an400", "amlogic,a311d2", "amlogic,t7";
interrupt-parent = <&gic>;
#address-cells = <2>;
#size-cells = <2>;
aliases {
serial0 = &uart_a;
};
memory@0 {
device_type = "memory";
reg = <0x00000000 0x00000000 0x00000000 0xe0000000
0x00000001 0x00000000 0x00000000 0x20000000>;
};
xtal: xtal-clk {
compatible = "fixed-clock";
clock-frequency = <24000000>;
clock-output-names = "xtal";
#clock-cells = <0>;
};
};
&uart_a {
clocks = <&xtal>, <&xtal>, <&xtal>;
clock-names = "xtal", "pclk", "baud";
status = "okay";
};
Annotation
- Immediate include surface: `amlogic-t7.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.