Give Me Back My GPIO Persistence Intro to the libgpiod GPIOManager
summary
Kernel-side GPIO persistence is rejected so userspace implements it: a new gpio-manager daemon (merged to master and planned for libgpiod 2.2) runs as a systemd service, exposes a DBus API, enforces permissions via a gpio group and sandboxing, and ships a command-line client gpiocli that lets scripts request, set, monitor and release lines without keeping a process alive. Behavior remains undefined for drivers that previously “kept” state, but the daemon centralizes control and works now for standard Linux systemd setups.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:59GPIO persistence problem
- 7:07GPIO Manager with D-Bus
- 10:39Practical usage with gpiod
- 13:33Key features
- 15:24Q&A
related talks
23mGive Me Back My GPIO Persistence Intro to the libgpiod GPIOManager
32mlibgpiod V2: New Major Release with a Ton of New Features
51mGPIO for Engineers and Makers
44mNew GPIO Interface for User Space
32mLibgpiod V2: New Major Release with a Ton of New Features
48mPin Control and GPIO Update
19mPinctrl and GPIO - Interactions and Footguns
37mIntroduction to Pin Muxing and GPIO Control Under Linux