arch/riscv/boot/dts/allwinner/sun20i-common-regulators.dtsi
Source file repositories/reference/linux-study-clean/arch/riscv/boot/dts/allwinner/sun20i-common-regulators.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/boot/dts/allwinner/sun20i-common-regulators.dtsi- Extension
.dtsi- Size
- 683 bytes
- Lines
- 29
- 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
- No C-style include directives detected by the generator.
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) 2021-2022 Samuel Holland <samuel@sholland.org>
/ {
reg_vcc: vcc {
compatible = "regulator-fixed";
regulator-name = "vcc";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
};
reg_vcc_3v3: vcc-3v3 {
compatible = "regulator-fixed";
regulator-name = "vcc-3v3";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
vin-supply = <®_vcc>;
};
};
&pio {
vcc-pb-supply = <®_vcc_3v3>;
vcc-pc-supply = <®_vcc_3v3>;
vcc-pd-supply = <®_vcc_3v3>;
vcc-pe-supply = <®_vcc_3v3>;
vcc-pf-supply = <®_vcc_3v3>;
vcc-pg-supply = <®_vcc_3v3>;
};
Annotation
- 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.