arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4b.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4b.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4b.dts- Extension
.dts- Size
- 917 bytes
- Lines
- 54
- 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
rk3399-nanopi-m4.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)
/*
* FriendlyElec NanoPi M4B board device tree source
*
* Copyright (c) 2020 Chen-Yu Tsai <wens@csie.org>
*/
/dts-v1/;
#include "rk3399-nanopi-m4.dtsi"
/ {
model = "FriendlyElec NanoPi M4B";
compatible = "friendlyarm,nanopi-m4b", "rockchip,rk3399";
adc-keys {
compatible = "adc-keys";
io-channels = <&saradc 1>;
io-channel-names = "buttons";
keyup-threshold-microvolt = <1500000>;
poll-interval = <100>;
button-recovery {
label = "Recovery";
linux,code = <KEY_VENDOR>;
press-threshold-microvolt = <18000>;
};
};
};
/* No USB type-C PD power manager */
/delete-node/ &fusb0;
&i2c4 {
status = "disabled";
};
&u2phy0_host {
phy-supply = <&vcc5v0_usb2>;
};
&u2phy0_otg {
phy-supply = <&vbus_typec>;
};
&u2phy1_otg {
phy-supply = <&vcc5v0_usb1>;
};
&vbus_typec {
enable-active-high;
gpios = <&gpio4 RK_PD2 GPIO_ACTIVE_HIGH>;
};
Annotation
- Immediate include surface: `rk3399-nanopi-m4.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.