arch/arm64/boot/dts/apple/t602x-j414-j416.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/apple/t602x-j414-j416.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/apple/t602x-j414-j416.dtsi- Extension
.dtsi- Size
- 785 bytes
- Lines
- 46
- 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
t600x-j314-j316.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
/*
* MacBook Pro (14/16-inch, 2022)
*
* This file contains the parts common to J414 and J416 devices with both t6020 and t6021.
*
* target-type: J414s / J414c / J416s / J416c
*
* Copyright The Asahi Linux Contributors
*/
/*
* These models are essentially identical to the previous generation, other than
* the GPIO indices.
*/
#include "t600x-j314-j316.dtsi"
&framebuffer0 {
power-domains = <&ps_disp0_cpu0>, <&ps_dptx_phy_ps>;
};
&hpm0 {
interrupts = <44 IRQ_TYPE_LEVEL_LOW>;
};
&hpm1 {
interrupts = <44 IRQ_TYPE_LEVEL_LOW>;
};
&hpm2 {
interrupts = <44 IRQ_TYPE_LEVEL_LOW>;
};
&hpm5 {
interrupts = <44 IRQ_TYPE_LEVEL_LOW>;
};
&wifi0 {
compatible = "pci14e4,4434";
};
&bluetooth0 {
compatible = "pci14e4,5f72";
};
Annotation
- Immediate include surface: `t600x-j314-j316.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.