arch/arm64/boot/dts/apple/t8012-jxxx.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/apple/t8012-jxxx.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/apple/t8012-jxxx.dtsi- Extension
.dtsi- Size
- 714 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
t8012.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
/*
* Common Device Tree for all T2 devices
*
* target-type: J132, J137, J140a, J140k, J152f, J160, J174, J185, J185f
* J213, J214k, J215, J223, J230k, J680, J780
*
* Copyright (c) 2024, Nick Chan <towinchenmi@gmail.com>
*/
#include "t8012.dtsi"
/ {
chassis-type = "embedded";
aliases {
serial0 = &serial0;
};
chosen {
#address-cells = <2>;
#size-cells = <2>;
ranges;
stdout-path = "serial0";
};
memory@800000000 {
device_type = "memory";
reg = <0x8 0 0 0>; /* To be filled by loader */
};
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
/* To be filled by loader */
};
};
&serial0 {
status = "okay";
};
Annotation
- Immediate include surface: `t8012.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.