Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Choose power management around the SoC’s real operating requirements: create separate voltage domains only where independent scaling or power control is useful, then match regulators, sequencing, monitoring, and software control to those domains. More domains can enable finer control, but they also add hardware and integration demands. There is no universal rail map or PMIC count; the target SoC and platform documentation must set the electrical details.

How many power domains does an SoC need?

Use the fewest domains that still provide the independence the design needs. Arm defines a voltage domain as “a collection of design elements supplied by a single voltage source.” A domain’s supply may be scaled or removed for power or performance reasons. Arm summarizes the architectural rationale: “A primary motivation for additional voltage domains is to support DVFS for functional areas of the SoC.” That is a reason to consider another domain, not a guarantee that adding one improves a product. Arm, Power Control System Architecture (2023)

Separate blocks when independent control has value

A useful boundary is one where a functional area has meaningfully different voltage or power needs and can operate independently without violating interface, timing, or platform constraints. For example, a design might consider separating memory-system logic from other system logic if independent scaling is useful. That is an option to evaluate, not a universal partition: DDR PHY and memory timing can constrain system-logic DVFS, and some peripherals may require fixed-frequency clocks.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Account for the cost of each boundary

Every additional voltage supply can mean another regulator and more sequencing, validation, and software coordination. The decision is therefore not simply “more domains save more power.” Compare the expected benefit of independent control with the cost and complexity of supplying, transitioning, monitoring, and validating it.

#1 Best Overall
Digilent Zybo Z7: Zynq-7000 ARM/FPGA SoC Development Board (Zybo Z7-10)
  • Zybo Z7 comes in two APSoC variants: Zybo Z7-10 features Xilinx XC7Z010-1CLG400C. Zybo Z7-20 features the larger Xilinx XC7Z020-1CLG400C. Either variant also has the option to add the SDSoC voucher.
  • A feature-rich, ready-to-use embedded software and digital circuit development board with a rich set of multimedia and connectivity peripherals to create a formidable single-board computer
  • Built around the Xilinx Zynq-7000 AP SoC, with 650MHz dual-core Cortex-A9 processor and DDR3 memory controller with 8 DMA channels
  • On board user interfaces include 6 push buttons, 4 slide switches, 5 LEDs, 2 RGB LEDs, and more
  • Expansion opportunities with six Pmod connector ports, over 30 FPGA I/O, four Analog capable 0-1.0V differential pairs to XADC, and more
  • Identify which functional areas need independent voltage scaling, power gating, or operating points.
  • Check fixed-frequency peripheral requirements and memory/DDR timing before drawing domain boundaries.
  • Confirm that a proposed boundary is supported by the SoC’s power architecture and the board’s electrical design.

What should a PMIC do in the power tree?

A PMIC is more than a voltage-conversion block. Depending on the selected device and platform, it may combine DC-DC conversion, LDO regulation, sequencing, programmable outputs, monitoring and control, and multiple operating modes. Discrete DC-DC converters and LDOs are alternatives when a design’s flexibility or cost considerations favor separate components. These are categories to compare, not a claim that one approach is inherently cheaper or better; check the selected component’s datasheet. Microchip Technology, “Why Choose a PMIC?”

Match functions to platform responsibilities

List which component or subsystem is responsible for each power-tree function rather than assuming the PMIC alone handles everything. Qualcomm’s Linux Boot Guide describes PMIC responsibilities that can include battery charging and gauging, user-interface components, and SoC infrastructure such as clocks, ADCs, and power-on functions. Its configurable PMIC device-tree properties describe Qualcomm’s boot flow; they are not requirements for every Linux platform. Qualcomm Linux Boot Guide

Rank #2
Digilent Zybo Z7: Zynq-7000 ARM/FPGA SoC Development Board (Zybo Z7-20)
  • Zybo Z7 comes in two APSoC variants: Zybo Z7-10 features Xilinx XC7Z010-1CLG400C. Zybo Z7-20 features the larger Xilinx XC7Z020-1CLG400C. Either variant also has the option to add the SDSoC voucher.
  • A feature-rich, ready-to-use embedded software and digital circuit development board with a rich set of multimedia and connectivity peripherals to create a formidable single-board computer
  • Built around the Xilinx Zynq-7000 AP SoC, with 650MHz dual-core Cortex-A9 processor and DDR3 memory controller with 8 DMA channels
  • On board user interfaces include 6 push buttons, 4 slide switches, 5 LEDs, 2 RGB LEDs, and more
  • Expansion opportunities with six Pmod connector ports, over 30 FPGA I/O, four Analog capable 0-1.0V differential pairs to XADC, and more

For each candidate PMIC or regulator arrangement, verify its supported rails and operating modes, programmable behavior, monitoring and fault handling, and sequencing capabilities against the SoC’s requirements. The architecture-level sources do not establish exact voltages, ramp rates, current limits, or fault responses for an unspecified design.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use platform examples as examples, not templates

Qualcomm’s QCS6490/QCS5430 component overview lists two mandatory core PMICs for the QCS6490: PM7325, which supplies most SoC subsystems with buck regulators and LDOs, and PM7350C, which supplies other subsystems with buck regulators, LDOs, and Buck-OR-Boost regulators. It separately lists the PMK7325 clock PMIC as mandatory, as well as optional or role-specific interface, camera, and supplementary charging components. This is one platform’s division of work, not a recommended count or set of part numbers for other SoCs. The overview was updated 2025-03-06. Qualcomm QCS6490 and QCS5430 Chipset Components Overview

Rank #3
Arty A7: Artix-7 FPGA Development Board for Makers and Hobbyists (Arty A7-100T)
  • Arty A7 comes in two FPGA variants: Arty A7-35T features Xilinx XC7A35TICSG324-1L. Arty A7-100T features the larger Xilinx XC7A100TCSG324-1.
  • Internal clock speeds exceeding 450MHz, On-chip analog-to-digital converter (XADC), Programmable over JTAG and Quad-SPI Flash
  • 256MB DDR3L with a 16-bit bus @ 667MHz, 16MB Quad-SPI Flash, USB-JTAG Programming circuitry, Powered from USB or any 7V-15V source
  • 10/100 Mbps Ethernet, USB-UART Bridge
  • 4 Switches, 4 Buttons, 1 Reset Button, 4 LEDs, 4 RGB LEDs, 4 Pmod connectors, shield connector

How do I integrate DVFS with a PMIC?

Treat DVFS as a coordinated platform capability, not a voltage command issued in isolation. A performance request can involve the operating point, regulator output, clocks, and power-domain state; software and firmware coordinate those resources through a platform-specific control path. Confirm who owns each transition and which combinations of voltage and frequency are supported before enabling them.

Connect operating points to hardware constraints

Build the supported voltage/frequency operating points from the target SoC and platform documentation. Then check transition constraints, fixed-frequency consumers, memory timing, and the PMIC’s ability to supply the required outputs. A domain that cannot change frequency dynamically, or a peripheral that depends on a fixed clock, must be reflected in the control policy rather than treated as freely scalable.

Rank #4
ZYNQ 7000 FPGA Development Board PZ7010 PZ7020 Starlite XC7Z010 XC7Z020 DDR3 USB Ethernet HDMI JTAG for Embedded Linux and FPGA Learning (PZ7020-SL-C, FPGA Board)
  • ZYNQ-7000 ARM+FPGA SoC: Powered by Xilinx ZYNQ XC7Z010/020 with dual-core ARM Cortex-A9 and programmable logic—ideal for embedded and FPGA development.
  • Integrated Interfaces for Versatile Applications: Features HDMI, USB 2.0 Host, UART, JTAG, Gigabit Ethernet (PS & PL), SD card, and 40-pin expansion for AD/DA, LCD, and camera modules.
  • Robust Memory & Storage: Equipped with 512MB/1GB DDR3, 128Mb QSPI Flash, 64Kbit EEPROM, and boot selection via JTAG/QSPI/SD for flexible design setups.
  • Industrial-Grade Design: Compact 90x60mm board with immersion gold finish, suitable for industrial environments. 5V/1A power input supports stable operation.
  • Support for Linux and Hardware Demos: Supports embedded Linux system, MIPI CSI camera input (7020 only), and comes with HDL demos—perfect for research and education.

Microchip’s SAMA7G5 documentation illustrates why support can vary by domain. For that processor, it lists CPU operating points of 90 MHz at 1.05 V, 250 MHz at 1.05 V, 600 MHz at 1.10 V, 800 MHz at 1.15 V, and 1 GHz at 1.25 V; it also says VDDCORE logic cannot have its frequency changed dynamically. These are SAMA7G5-specific documented values, not targets for another SoC. Microchip Technology, SAMA7G5 VDDCORE and VDDCPU Dynamic Power

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Assign control across the operating system and firmware

The division of work depends on the platform. Arm’s Zena documentation describes CPUIdle for idle states and CPUFreq for active frequency/voltage operating points, with SCMI as the protocol between OS power-management software and a platform SCP. Qualcomm’s SCMI example describes a power-domain transition coordinating clocks, regulators, and physical-domain activation and initialization; power-off reverses those resources. The particular responsibilities and sequencing must be taken from the target platform’s guidance. Arm Zena power and performance control; Qualcomm, “SCMI: abstracting platform resources using power and performance domains in Linux” (2024)

Control can also be distributed within firmware. Arm’s Neoverse reference design describes per-application-processor DVFS supported by local control processors (LCPs) under a system control processor (SCP), as a way to scale control with core count and avoid placing all per-core work on the SCP. This is a reference-design approach, not a universal architectural requirement. Arm Neoverse Reference Design LCP documentation

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

A practical power-tree design sequence

  1. Start with documented loads and states. Gather the SoC’s power-domain definitions, supported operating points, memory and peripheral constraints, and required power states from the target platform documentation.
  2. Choose domain boundaries. Separate areas only where independent scaling or power control is needed and feasible. Evaluate the resulting regulator and sequencing burden alongside the expected control benefit.
  3. Allocate supply functions. Decide which outputs and system duties belong to a PMIC and which, if any, belong to discrete regulators. Check the chosen components’ datasheets for electrical limits, programmability, monitoring, modes, and sequencing behavior.
  4. Define the transition owner and path. Document how OS policy, firmware, regulators, clocks, and physical power domains cooperate for each supported transition. Use the platform’s SCMI or vendor-specific mechanism as applicable; do not assume that a control interface has identical responsibilities across systems.
  5. Validate the complete set of states and transitions. Check supported voltage/frequency combinations, transition constraints, sequencing, monitoring, and fault response against the SoC, PMIC, memory, board, and software documentation. Resolve exact rail values, ramp rates, current budgets, decoupling, and ordering from those platform specifications rather than generic guidance.

How to compare valid alternatives

Decision What to compare Tradeoff to resolve
More versus fewer voltage domains Which blocks need independent scaling or power gating; peripheral clock and DDR/memory constraints; additional supplies and regulators. Finer independent control versus regulator, sequencing, software, and validation demands. Arm identifies added regulators as a cost of additional supplies. Arm, Power Control System Architecture (2023)
Integrated PMIC versus discrete regulation Required DC-DC and LDO outputs, programmability, sequencing, monitoring, operating modes, board needs, and cost priorities. Choose the component arrangement that fits the platform’s needs; Microchip identifies both PMICs and discrete DC-DC/LDO components as possible approaches but supplies no universal cost or performance winner. Microchip Technology
Centralized versus distributed control Per-domain and per-core control needs, OS-to-firmware interface, platform SCP responsibilities, and any local control processors. Compare control scalability and integration fit using the selected platform’s design; Arm’s LCP arrangement is one reference design, not a requirement. Arm Neoverse Reference Design

The decisive review artifact is a platform-specific map that connects each domain and supported operating state to its supply, regulator behavior, clock dependencies, transition owner, and verification source. Without the target SoC, PMIC, memory, board, and software specifications, an exact rail map or sequencing prescription cannot be established.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.