arch/arm64/boot/dts/nvidia/tegra210-p3541-0000.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/nvidia/tegra210-p3541-0000.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/nvidia/tegra210-p3541-0000.dts- Extension
.dts- Size
- 1037 bytes
- Lines
- 60
- 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
tegra210-p3450-0000.dts
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/dts-v1/;
#include "tegra210-p3450-0000.dts"
/ {
model = "NVIDIA Jetson Nano 2GB Developer Kit";
compatible = "nvidia,p3541-0000", "nvidia,p3450-0000", "nvidia,tegra210";
memory@80000000 {
reg = <0x0 0x80000000 0x0 0x80000000>;
};
host1x@50000000 {
sor@54540000 {
status = "disabled";
};
dpaux@545c0000 {
status = "disabled";
};
};
padctl@7009f000 {
ports {
usb2-1 {
vbus-supply = <&vdd_hub_5v0>;
};
usb2-2 {
vbus-supply = <&vdd_hub_5v0>;
};
usb3-0 {
/delete-property/ vbus-supply;
};
};
};
regulator-vdd-hdmi-5v0 {
gpio = <&gpio TEGRA_GPIO(A, 6) GPIO_ACTIVE_HIGH>;
enable-active-high;
};
/delete-node/ regulator-vdd-hub-3v3;
vdd_hub_5v0: regulator-vdd-hub-5v0 {
compatible = "regulator-fixed";
regulator-name = "VDD_HUB_5V0";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
gpio = <&gpio TEGRA_GPIO(I, 2) GPIO_ACTIVE_HIGH>;
enable-active-high;
vin-supply = <&vdd_5v0_sys>;
};
};
Annotation
- Immediate include surface: `tegra210-p3450-0000.dts`.
- 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.