This article explains how to adopt Linux kernel's struct‑array initialization and device‑tree matching techniques to implement a flexible C‑based UART driver that supports multiple compression configurations, complete with code examples and compilation guidance.
This article provides a comprehensive overview of U‑Boot, covering its definition, boot stages, environment variables, command system, device‑tree usage, network and storage support, security features, debugging techniques, performance tuning, platform migration steps, and a comparison with other bootloaders, all illustrated with concrete code examples and tables.
This article presents an isolation‑focused multi‑kernel architecture that replaces replica‑based designs with dynamic resource management using device‑tree overlays, reuses existing Linux mechanisms such as kexec and hot‑plug, and enables zero‑downtime updates, hardware‑queue isolation, and fault‑tolerant kernel recovery for modern cloud infrastructures.
This article explains the role of Device Tree in embedded Linux, its history, file formats, compilation methods, syntax details, and provides practical examples—including GPIO, LED, and custom sensor implementations—to help developers create and integrate custom hardware descriptions efficiently.
This article provides an in‑depth, step‑by‑step analysis of Linux GICv3 interrupt architecture, the kernel driver initialization, hardware‑to‑virtual interrupt mapping, the full interrupt handling state machine, and the workqueue subsystem including its data structures, initialization, and usage patterns.
This article explores the Linux kernel's interrupt management architecture, detailing how hardware interrupt IDs are mapped to software IRQ numbers through the irq_domain structure, GIC controller design, and various mapping strategies such as linear, radix‑tree, and no‑map approaches.
This guide explains why and how to implement MDIO over GPIO on a Linux system, covering MDIO fundamentals, Clause22/Clause45 frame structures, YT8521 PHY pinout, required kernel drivers, device‑tree configuration, log verification, and command‑line usage.
The article traces the Android fingerprint driver’s boot‑to‑initialization sequence in Linux kernel 5.10, detailing how fp_init and fp_probe are scheduled, how the Device Tree is parsed and turned into platform devices, and explains the three driver‑DTS matching mechanisms, offering insights applicable to other platform drivers.
This article explains how to build a modular, device‑agnostic LCD driver architecture for STM32 boards, covering hardware scenarios, object‑oriented C design, driver‑device separation, and practical code examples for TFT, COG, and OLED displays.
This article shares practical insights from a Linux driver engineer on device trees, cross‑compilation toolchains, filesystem considerations, kernel configuration, and debugging techniques that every newcomer should understand to avoid common pitfalls and integrate drivers successfully.
This guide explains Linux GPIO fundamentals, driver APIs for requesting, configuring, and reading/writing pins, and demonstrates how to use the pinctrl subsystem with device‑tree examples for both single GPIOs and GPIO arrays.
This guide introduces Linux Device Tree concepts, explains why it was added to the kernel, details its syntax and standard properties, describes common nodes, and provides practical examples of OF functions for accessing nodes and properties in kernel code.
The article explains how the Linux kernel translates ARM GIC hardware interrupt numbers into virtual software IRQs by maintaining a global bitmap, initializing the interrupt controller, using irq_domain structures to map and associate hwirq and virq values, and storing relationships in descriptor and revmap trees for efficient lookup.
This article systematically explains the Linux driver ecosystem by covering the bus‑device‑driver model, the role of device trees in decoupling hardware description from driver code, and step‑by‑step guidance for creating a custom development board with full DTS and kernel integration.
The article explains Android’s Device Tree workflow, detailing how DTS files are compiled into DTB blobs and, since Android 8, split into platform DTB and vendor DTBO partitions, how GKI moves DTB to vendor_boot, and how bootloaders and runtime stages match DTBs/DTBOs using platform IDs, GPIO cues, and overlay mechanisms.
This guide explains how the of_device_id structure and of_device_get_match_data() function enable flexible device matching in ARM‑based SoCs, covering their definitions, usage patterns, code examples, troubleshooting tips, and how to expose device tables to user space.
The article explains Device Tree fundamentals—defining DTS, DTSI, DTB and DTBO formats, their origin as a cleaner alternative to kernel‑embedded platform code, how overlays decouple vendor changes via matching project and PCB IDs, the rules for modifying nodes, and debugging techniques using dtc and mkdtimgdump tools.
This guide outlines six effective debugging techniques—including dtdiff, kernel device‑tree inspection, U‑Boot fdt commands, dtc decompilation, kernel fdt inspection, and of_property APIs—to help developers quickly locate and resolve device‑tree‑related issues during driver development.
This article explains how infrared remote controls work, details the NEC protocol timing and encoding, and walks through the Linux kernel driver implementation—including GPIO‑IR receiver code, NEC decoder logic, device‑tree configuration, and key‑event reporting—providing a complete technical guide for developers.
postmarketOS, an Alpine‑Linux based OS for legacy smartphones, now runs on roughly 200 mobile devices, highlighting the challenges of ARM porting, the role of pmbootstrap tools, and the community’s drive to extend device lifespans despite hardware and driver hurdles.
