arch/arm/boot/dts/aspeed/ibm-power9-dual.dtsi
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/aspeed/ibm-power9-dual.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/aspeed/ibm-power9-dual.dtsi- Extension
.dtsi- Size
- 3741 bytes
- Lines
- 249
- 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
- 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+
// Copyright 2018 IBM Corp
&fsi {
cfam@0,0 {
reg = <0 0>;
#address-cells = <1>;
#size-cells = <1>;
chip-id = <0>;
scom@1000 {
compatible = "ibm,fsi2pib";
reg = <0x1000 0x400>;
};
i2c@1800 {
compatible = "ibm,fsi-i2c-master";
reg = <0x1800 0x400>;
#address-cells = <1>;
#size-cells = <0>;
cfam0_i2c0: i2c-bus@0 {
reg = <0>;
};
cfam0_i2c1: i2c-bus@1 {
reg = <1>;
};
cfam0_i2c2: i2c-bus@2 {
reg = <2>;
};
cfam0_i2c3: i2c-bus@3 {
reg = <3>;
};
cfam0_i2c4: i2c-bus@4 {
reg = <4>;
};
cfam0_i2c5: i2c-bus@5 {
reg = <5>;
};
cfam0_i2c6: i2c-bus@6 {
reg = <6>;
};
cfam0_i2c7: i2c-bus@7 {
reg = <7>;
};
cfam0_i2c8: i2c-bus@8 {
reg = <8>;
};
cfam0_i2c9: i2c-bus@9 {
reg = <9>;
};
cfam0_i2c10: i2c-bus@a {
reg = <10>;
};
cfam0_i2c11: i2c-bus@b {
reg = <11>;
};
cfam0_i2c12: i2c-bus@c {
Annotation
- 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.