Introducing the Zephyr Input Subsystem
summary
A new Zephyr input subsystem lands in 3.4 and implements a Linux‑style event model so drivers report typed events with optional sync semantics; it supports many-to-many listeners registered at build time, offers lightweight synchronous callbacks and an asynchronous thread mode with a message queue, includes a kscan compatibility translator and a sample long-press filter, is already porting drivers, plans optional zbus integration, and aims to replace kscan without breaking existing users.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:49Limitations of K-scan API
- 5:00Previous K-scan replacements
- 6:43Linux input API inspiration
- 9:11Requirements for new subsystem
- 10:39Design of new subsystem
- 12:49Driver and app API
- 14:34Synchronous vs thread mode
- 15:35Case scan compatibility
- 16:57Extensibility and vendor codes
- 17:40Input event filters
- 18:43Event system integration
- 20:49Input handling in other projects
- 21:53Current status and plans
- 23:18Q&A
related talks
38mVideo4Zephyr: From Basic APIs Towards a Full-fledged Video Subsystem- 38mVideo4Zephyr: From Basic APIs Towards a Full-fledged Video Subsystem
37mZephyr: A Game Changer for the Automotive Industry
31mA Zephyr User Story
07mLightning Talk: Introducing the New Zephyr Stepper Driver API
23mA Dive into Zephyr Device Driver Model
41mFuture of Zephyr Device Model
49mThe Zephyr™ Project – An Updated Overview