arch/riscv/boot/dts/microchip/mpfs-icicle-kit-prod.dts
Source file repositories/reference/linux-study-clean/arch/riscv/boot/dts/microchip/mpfs-icicle-kit-prod.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/boot/dts/microchip/mpfs-icicle-kit-prod.dts- Extension
.dts- Size
- 668 bytes
- Lines
- 34
- Domain
- Architecture Layer
- Bucket
- arch/riscv
- 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
mpfs-icicle-kit-common.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)
/* Copyright (c) 2025 Microchip Technology Inc */
/dts-v1/;
#include "mpfs-icicle-kit-common.dtsi"
/ {
model = "Microchip PolarFire-SoC Icicle Kit (Production Silicon)";
compatible = "microchip,mpfs-icicle-prod-reference-rtl-v2507",
"microchip,mpfs-icicle-kit-prod",
"microchip,mpfs-icicle-kit",
"microchip,mpfs-prod",
"microchip,mpfs";
};
&i2c0 {
pinctrl-names = "default";
pinctrl-0 = <&i2c0_fabric>;
};
&i2c1 {
pinctrl-names = "default";
pinctrl-0 = <&i2c1_mssio>;
};
&syscontroller {
microchip,bitstream-flash = <&sys_ctrl_flash>;
};
&syscontroller_qspi {
status = "okay";
};
Annotation
- Immediate include surface: `mpfs-icicle-kit-common.dtsi`.
- Atlas domain: Architecture Layer / arch/riscv.
- 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.