arch/arm64/boot/dts/apple/t6020-j474s.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/apple/t6020-j474s.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/apple/t6020-j474s.dts- Extension
.dts- Size
- 891 bytes
- Lines
- 48
- 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
t6020.dtsit602x-j474-j475.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
/*
* Mac mini (M2 Pro, 2023)
*
* target-type: J474s
*
* Copyright The Asahi Linux Contributors
*/
/dts-v1/;
#include "t6020.dtsi"
/*
* This model is very similar to M1 and M2 Mac Studio models so base it on those
* and remove the missing SDHCI controller.
*/
#include "t602x-j474-j475.dtsi"
/ {
compatible = "apple,j474s", "apple,t6020", "apple,arm-platform";
model = "Apple Mac mini (M2 Pro, 2023)";
};
/* PCIe devices */
&wifi0 {
compatible = "pci14e4,4434";
brcm,board-type = "apple,tasmania";
};
&bluetooth0 {
compatible = "pci14e4,5f72";
brcm,board-type = "apple,tasmania";
};
/*
* port01 is unused, remove the PCIe sdhci0 node from t600x-j375.dtsi and adjust
* the iommu-map.
*/
/delete-node/ &sdhci0;
&pcie0 {
iommu-map = <0x100 &pcie0_dart_0 1 1>,
<0x200 &pcie0_dart_2 1 1>,
<0x300 &pcie0_dart_3 1 1>;
};
Annotation
- Immediate include surface: `t6020.dtsi`, `t602x-j474-j475.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.