arch/arm64/boot/dts/freescale/s32n79-rdb.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/s32n79-rdb.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/s32n79-rdb.dts- Extension
.dts- Size
- 984 bytes
- Lines
- 71
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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
s32n79.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 BSD-3-Clause)
/*
* Copyright 2026 NXP
*
* NXP S32N79 Reference Design Board (S32N79-RDB)
*/
/dts-v1/;
#include "s32n79.dtsi"
/ {
compatible = "nxp,s32n79-rdb", "nxp,s32n79";
model = "NXP S32N79-RDB";
aliases {
serial0 = &uart0;
serial1 = &uart5;
serial2 = &uart6;
serial3 = &uart7;
};
chosen {
stdout-path = "serial0:115200n8";
};
reserved-memory {
ranges;
#address-cells = <2>;
#size-cells = <2>;
scmi_shbuf: memory@93000000 {
compatible = "arm,scmi-shmem";
reg = <0x0 0x93000000 0x0 0x80>;
no-map;
};
};
memory@80000000 {
reg = <0x00 0x80000000 0x00 0x80000000>,
<0x88 0x00000000 0x03 0x40000000>,
<0xc0 0x00000000 0x03 0x40000000>;
device_type = "memory";
};
};
&irqsteer_coss {
status = "okay";
};
&uart0 {
status = "okay";
};
&uart5 {
status = "okay";
};
&uart6 {
status = "okay";
};
&uart7 {
status = "okay";
};
&usdhc0 {
disable-wp;
no-sdio;
status = "okay";
};
Annotation
- Immediate include surface: `s32n79.dtsi`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.