arch/riscv/boot/dts/renesas/r9a07g043f01-smarc.dts
Source file repositories/reference/linux-study-clean/arch/riscv/boot/dts/renesas/r9a07g043f01-smarc.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/boot/dts/renesas/r9a07g043f01-smarc.dts- Extension
.dts- Size
- 681 bytes
- Lines
- 28
- 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
r9a07g043f.dtsirzfive-smarc-som.dtsirzfive-smarc.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-only OR BSD-2-Clause)
/*
* Device Tree Source for the RZ/Five SMARC EVK
*
* Copyright (C) 2022 Renesas Electronics Corp.
*/
/dts-v1/;
/*
* DIP-Switch SW1 setting
* 1 : High; 0: Low
* SW1-2 : SW_SD0_DEV_SEL (0: uSD; 1: eMMC)
* SW1-3 : SW_ET0_EN_N (0: ETHER0; 1: CAN0, CAN1, SSI1, RSPI1)
* Please change below macros according to SW1 setting on the SoM
*/
#define SW_SW0_DEV_SEL 1
#define SW_ET0_EN_N 1
#include "r9a07g043f.dtsi"
#include "rzfive-smarc-som.dtsi"
#include "rzfive-smarc.dtsi"
/ {
model = "Renesas SMARC EVK based on r9a07g043f01";
compatible = "renesas,smarc-evk", "renesas,r9a07g043f01", "renesas,r9a07g043";
};
Annotation
- Immediate include surface: `r9a07g043f.dtsi`, `rzfive-smarc-som.dtsi`, `rzfive-smarc.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.