Power Management Integrated Circuits: Keep the Power in Your Hands
Power Management Integrated Circuits: Keep the Power in Your Hands - Quentin Schulz, Free Electrons
Modern embedded platforms are most likely to embed a Power Management Integrated Circuit (PMIC). This component provides the different regulators to the board, controls which external power supply is used, recharges batteries, protects the board of over-voltage, etc.
Within the Linux kernel, such PMICs are typically handled via a combination of drivers in the IIO, MFD, power supply and regulator frameworks, and this talk proposes a walk-through how a PMIC is supported using these different subsystems.
To illustrate this presentation, the example of the X-Powers PMICs, which are frequently used in numerous Allwinner ARM platforms, will be used.
About Quentin Schulz Quentin joined Free Electrons in mid-2016 as an embedded Linux engineer after spending a 6-months internship designing, building and integrating a farm to Kernel CI. He has been especially working on adding support for the ADC of Allwinner SoCs and for power supplies drivers of X-Powers PMICs, often seen on the same boards. He spoke about kernel Continuous Integration with LAVA and KernelCI at the 2016 ELCE in Berlin.
Embedded systems are increasingly composed of IP cores and chips assembled to create advanced features. Display devices are no exception and comprise components that get reused from system to system. With their roots in the the desktop world, Linux display APIs haven't been developed with this architecture in mind and don't maximize flexibility and code reusability. The Common Display Framework will reshape the display architecture in a modular and more future-proof way. It creates separate drivers for distinct components in the display pipeline and orchestrates communication between them. This talk will present ongoing work on CDF and will discuss future directions for userspace API enhancements. This talk is addressed to developers who want to learn about tomorrow's Linux kernel display architecture. Familiarity with the basic display concepts is recommended but not mandatory.
ARM64 SoC Linux Support Check-List - Gregory Clement, Free Electrons
The ARM64 support in the kernel is mature, and we see more and more ARMv8 based SoCs being supported in the Linux kernel. It is now time to make the checklist of all what should be done in order to add the support for a new ARM64 SoC into the kernel. This talk will be an update of the talk made in early 2013 about ARM SoCs, with the addition of ARM64 specifities and various updates on the common parts between ARM32 and ARM64.
About Gregory Clement
Gregory Clement is an embedded Linux engineer and trainer at Free Electrons since 2010. He has 15 years of on the field experience in porting and operating embedded Linux on many hardware architectures. He is currently involved in the integration of Marvell Armada 370/375/38x/39x/XP and the new ARM64 37xx/7K/8K SoC support in the mainline Linux kernel, acting as co-maintainer for the mvebu ARM sub-architecture (which includes the orion5x, mv78x00, kirkwood, dove and Armada from 370 to 7K/8K SoCs).
Přednáška na konferenci InstallFest 2020
(https://installfest.cz/if20)
Abstrakt:
Tato přednáška nabízí posluchači vhled do mobilního světa GNU/Linuxu a možností, které dokáže i uživateli nabídnout. V době, kdy je svoboda a soukromí velice aktuální téma si tato přednáška si klade za cíl objasnit většinu dotazů, které si běžný uživatel klade při setkání s pojmy mobilní Linux.
V první části nahlédneme do historie vývoje a popíšeme si aktuální situaci v které se momentálně mobilní linuxový ekosystém nachází a jak si dnes stojí oproti své konkurenci.
V druhé části prozkoumáme uživatelské rozhraní (UI) dostupné na linuxových telefonech a tabletech. Terminál na telefonu je cool, ale máme k dispozici prostředí, které by mohl používat i běžný uživatel?
V třetí části se seznámíme s oficiálně vyráběnými linuxovými telefony a položíme otázku co dokáží nabídnout oproti komunitou spravovaným zažízením?
To nás dovedlo na konec, kde si dovolím pro pokročilejší zmínít možnosti zprovoznění na již existujícím hardwaru (včetně živé ukázky běhu na tabletu Nexus 7).
Vyrobilo AVC Silicon Hill, 2020.
Thomas Petazzoni
From mobile devices to industrial equipment, and with the rise of IoT, computing systems based on the ARM architecture are already ubiquitous and will become even more so in the future, which means more and more developers will be exposed to ARM systems.
The ARM architecture however has a number of differences compared to x86/x86_64, both in how the hardware is designed, and how it is supported from a low-level software point of view: at the bootloader level and the Linux kernel level.
This talk proposes an introduction to the ARM architecture, to help Linux users and developers understand the huge variety of ARM processors and platforms that are available, and how such a variety of hardware is supported in bootloaders and the kernel.
If you want to migrate your system to an ARM platform, and understand the difference between the Raspberry Pi variants, between ARMv6, ARMv7 and ARMv8, what is the Device Tree, what is this U-Boot thing, and generally get a better understanding of the ARM platform, this talk is for you!
The common clock framework, which was included in the 3.4 kernel in the beginning of 2012, is now mandatory to support all new ARM SoCs. It is also part of the _one zImage to run them all_ big plan of the ARM architecture in the Linux kernel. After an introduction on why we needed this framework and on the problems it solves, we will go through the implementation details of this framework. Then, with real examples, we will focus on how to use this framework to add clock support to a new ARM SoC. We will also show how the device tree is used in this process. The last part of the talk will review how device drivers use this framework, using examples taken from various parts of the kernel.This talk is an update of the one given at ELC 2013. It will cover the new features introduced since the beginning of the year.
The conversion of the ARM Linux kernel over to the Device Tree as the mechanism to describe the hardware has been a significant change for ARM kernel developers. Nowadays, all developers porting the Linux kernel on new ARM platforms, either new SOCs or new boards, have to work with the Device Tree. Based on practical examples, this talk intends to provide a _getting started guide_ for newcomers in the Device Tree world: what is the Device Tree? How is it written and compiled? How do the bootloader and kernel interact? How are Device Tree bindings written and documented? What are the best practices for writing Device Trees and the bindings?
Demystifying Linux MIPI DSI Subsystem - Jagan Teki, Amarula Solutions
Today every modern multimedia supported SoC's comprises of variety of display controller interfaces bounded with LCD panels or bridges and a GPU, to provide display acceleration. Out of many display controller interfaces the MIPI Display Serial Interface (MIPI DSI) is a versatile, high-speed interface for smartphones, tablets, laptops, automotive and other platforms. The Linux kernel support these controller interfaces via DRM subsystem with underlying DSI controllers, panels, bridges drivers.This talk start with a brief overview of Linux DRM subsystem with bounded display controller interfaces like HDMI, RGB, LVDS and DSI and then the talk switch to traverse more details about Linux MIPI DSI controller, DPHY, DSI panel, DSI bridge interfaces drivers along with how these display drivers are interact with GPU drivers. This talk is based on the work done on Allwinner MIPI DSI controller with variety of associated LCD panels, bridges by validating these interfaces via ARM Mali GPU.
But what are these ""Clocks"" stuff I see in the kernel about ?
Since first introduction of linux/clk.h in 2006 from Russel King, clock management was progressively part of the needed system management and resource handling in drivers.
Then, in 2012, Mike Turquette introduced the ""Common Clock Framework"" he co-maintained with Steven Boyd, becoming a central ""Framework"" handling clocks over the system to provide controls by the device drivers.
- However, what are these clocks?
- What are they in physical terms?
- How are they modeled in Hardware?
- Why do we need them to control internal&external devices?
Neil will make a full overview of the ""Common Clock Framework"", how it's integrated in the Linux Kernel and a brief overview of the physical implementation&requirement in Hardware.
References
This talk was given on the 2020 Edition of the Virtual Embedded Linux Conference Europe
Slides are available at: https://static.sched.com/hosted_files/osseu2020/45/ELC-E%202020_%20What%20The%20Clock%20%21.pdf
Follow Live Embedded Event on :
- Twitter : https://twitter.com/LiveEmbedded