Give Me Back My GPIO Persistence Intro to the libgpiod GPIOManager
summary
Claim is that kernel persistence is rejected so a user‑space daemon solves it: libgpiod now includes gpio-manager, a two‑year effort merged to master and slated for 2.2, that runs as a systemd service with sandboxing and enforces access via group rules. It exposes a DBus API and a companion gpiocli CLI so scripts can request lines, exit, and have the daemon hold ownership; it is implemented, available now, and asking for testing and reviews.
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
32mLibgpiod V2: New Major Release with a Ton of New Features
44mNew GPIO Interface for User Space
51mGPIO for Engineers and Makers
35mCompound Interest - Dealing with Two Decades of Technical Debt in Embedded...
48mPin Control and GPIO Update
37mIntroduction to Pin Muxing and GPIO Control Under Linux