arch/arm64/boot/dts/qcom/sc8280xp-el2.dtso
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/sc8280xp-el2.dtso
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/sc8280xp-el2.dtso- Extension
.dtso- Size
- 770 bytes
- Lines
- 43
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- Inferred role
- Architecture Layer: arch/arm64
- 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: BSD-3-Clause
/*
* sc8280xp specific modifications required to boot in EL2.
*/
/dts-v1/;
/plugin/;
/* We can't and don't need to use zap shader in EL2 as linux can zap the gpu on it's own. */
&gpu_zap_shader {
status = "disabled";
};
/*
* When running under QHEE, this IOMMU is controlled by the firmware,
* however when we take ownership of it in EL2, we need to configure
* it properly to use PCIe.
*/
&pcie2a {
iommu-map = <0 &pcie_smmu 0x20000 0x10000>;
};
&pcie2b {
iommu-map = <0 &pcie_smmu 0x30000 0x10000>;
};
&pcie3a {
iommu-map = <0 &pcie_smmu 0x40000 0x10000>;
};
&pcie3b {
iommu-map = <0 &pcie_smmu 0x50000 0x10000>;
};
&pcie4 {
iommu-map = <0 &pcie_smmu 0x60000 0x10000>;
};
&pcie_smmu {
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.