arch/arm64/boot/dts/apple/t7000-handheld.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/apple/t7000-handheld.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/apple/t7000-handheld.dtsi- Extension
.dtsi- Size
- 630 bytes
- Lines
- 32
- 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
- No C-style include directives detected by the generator.
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
/*
* Apple iPhone 6, iPhone 6 Plus, iPad mini 4, iPod touch 6
*
* This file contains the parts common to handheld devices with t7000
*
* target-type: J96, J97, N56, N61, N102
*
* Copyright (c) 2024, Nick Chan <towinchenmi@gmail.com>
*/
/ {
chosen {
stdout-path = "serial0";
framebuffer0: framebuffer@0 {
compatible = "apple,simple-framebuffer", "simple-framebuffer";
reg = <0 0 0 0>; /* To be filled by loader */
/* Format properties will be added by loader */
status = "disabled";
};
};
};
&dwi_bl {
status = "okay";
};
&serial0 {
status = "okay";
};
Annotation
- 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.