arch/powerpc/boot/dts/fsl/t1040rdb.dts
Source file repositories/reference/linux-study-clean/arch/powerpc/boot/dts/fsl/t1040rdb.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/boot/dts/fsl/t1040rdb.dts- Extension
.dts- Size
- 4299 bytes
- Lines
- 189
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- 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
t1040si-post.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
/include/ "t104xsi-pre.dtsi"
/include/ "t104xrdb.dtsi"
/ {
model = "fsl,T1040RDB";
compatible = "fsl,T1040RDB";
aliases {
phy_sgmii_2 = &phy_sgmii_2;
};
soc@ffe000000 {
fman@400000 {
ethernet@e0000 {
fixed-link = <0 1 1000 0 0>;
phy-connection-type = "sgmii";
};
ethernet@e2000 {
fixed-link = <1 1 1000 0 0>;
phy-connection-type = "sgmii";
};
ethernet@e4000 {
phy-handle = <&phy_sgmii_2>;
phy-connection-type = "sgmii";
};
mdio@fc000 {
phy_sgmii_2: ethernet-phy@3 {
reg = <0x03>;
};
/* VSC8514 QSGMII PHY */
phy_qsgmii_0: ethernet-phy@4 {
reg = <0x4>;
};
phy_qsgmii_1: ethernet-phy@5 {
reg = <0x5>;
};
phy_qsgmii_2: ethernet-phy@6 {
reg = <0x6>;
};
phy_qsgmii_3: ethernet-phy@7 {
reg = <0x7>;
};
/* VSC8514 QSGMII PHY */
phy_qsgmii_4: ethernet-phy@8 {
reg = <0x8>;
};
phy_qsgmii_5: ethernet-phy@9 {
reg = <0x9>;
};
phy_qsgmii_6: ethernet-phy@a {
reg = <0xa>;
};
phy_qsgmii_7: ethernet-phy@b {
reg = <0xb>;
};
};
};
};
Annotation
- Immediate include surface: `t1040si-post.dtsi`.
- Atlas domain: Architecture Layer / arch/powerpc.
- 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.