Big.LITTLE software is not so hard
Brian Jeff, ARM
EETimes (10/9/2012 4:44 AM EDT)
One of the questions I get asked most often about ARM big.LITTLE processor technology is, "how complicated is the software?"
In big.LITTLE processors, there are two distinct CPU clusters in the applications processor subsystem, one designed for optimum energy efficiency and the other designed for maximum performance in the device power budget. Software dynamically and seamlessly moves to the right-sized ARM Cortex core, either big or LITTLE, for the work at hand. This sounds quite complicated, but in reality it is an extension of the operating system power management software in wide use today on mobile phone SoCs.
To read the full article, click here
Related Semiconductor IP
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
Related Articles
- Big.LITTLE processing with ARM Cortex-A15 & Cortex-A7
- Bridging software and hardware to accelerate SoC validation
- Software generated BCH as a way to solve challenges of providing multiple configuration IP
- Density Requirements at 28 nm
Latest Articles
- A Secure dToF LiDAR SoC with Dual-Domain Fingerprinting and Event-Driven AFE Circuit Achieving Sensor-Level Attack Resilience
- ZTA-Q: an Open-source RISC-V Platform for Accurate Quantized CNN Inference
- Automated Pre-Silicon Verification of High-Speed DDR5 and LPDDR5/6 Memory Controllers: Closed-Loop Timing, Mode Register, and PHY Synchronization in UVM
- U-Sonic: An Open-Source 8-Channel Ultrasound Transmit IP in a 130 nm RISC-V SoC
- S-ALSA: Co-Design of Adiabatic Logic-based Sensing and Balanced Bit-Cells for Secure and Energy-Efficient MRAM