arch/arm/boot/dts/aspeed/ibm-power10-quad.dtsi
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/aspeed/ibm-power10-quad.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/aspeed/ibm-power10-quad.dtsi- Extension
.dtsi- Size
- 24255 bytes
- Lines
- 1310
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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
ibm-power10-dual.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-later
// Copyright 2023 IBM Corp.
#include "ibm-power10-dual.dtsi"
&cfam0_i2c0 {
i2cr@20 {
compatible = "ibm,i2cr-fsi-master";
reg = <0x20>;
#address-cells = <2>;
#size-cells = <0>;
cfam@0,0 {
reg = <0 0>;
#address-cells = <1>;
#size-cells = <1>;
chip-id = <0>;
scom100: scom@1000 {
compatible = "ibm,i2cr-scom";
reg = <0x1000 0x400>;
};
sbefifo100: sbefifo@2400 {
compatible = "ibm,p9-sbefifo";
reg = <0x2400 0x400>;
#address-cells = <1>;
#size-cells = <0>;
};
};
};
};
&cfam0_i2c1 {
i2cr@20 {
compatible = "ibm,i2cr-fsi-master";
reg = <0x20>;
#address-cells = <2>;
#size-cells = <0>;
cfam@0,0 {
reg = <0 0>;
#address-cells = <1>;
#size-cells = <1>;
chip-id = <0>;
scom101: scom@1000 {
compatible = "ibm,i2cr-scom";
reg = <0x1000 0x400>;
};
sbefifo101: sbefifo@2400 {
compatible = "ibm,p9-sbefifo";
reg = <0x2400 0x400>;
#address-cells = <1>;
#size-cells = <0>;
};
};
};
};
&cfam0_i2c10 {
i2cr@20 {
compatible = "ibm,i2cr-fsi-master";
reg = <0x20>;
#address-cells = <2>;
#size-cells = <0>;
cfam@0,0 {
reg = <0 0>;
Annotation
- Immediate include surface: `ibm-power10-dual.dtsi`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.