The Serial Device Bus
summary
The kernel now includes the Serial Device Bus (merged around 4.11/4.12) which registers serial-attached clients from firmware so Bluetooth, NFC and GPS appear as real devices instead of user-space daemons; it adds a TTY port controller and device tree bindings so clients can declare GPIOs, clocks and regulators and use kernel firmware and PM. Current limits: single-slave only, no input pushback (lost RX at high rates), no bus runtime-PM propagation, and no hot‑plug/RS‑485/mux support yet.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:19TTY Layer
- 3:51User-Space Drivers
- 5:58Bluetooth Example
- 8:03The Serial Devices
- 12:52Device Tree Bindings
- 16:08Driver Interface Callbacks
- 17:00Example Driver Probe
- 17:43Limitations
- 24:44Merged Drivers
- 28:38Future Work
- 29:55Further Reading
related talks
55mBluetooth on Embedded Linux Systems Deep Dive
01h 00mGroking the Linux SPI Subsystem
28mEmulating Devices in Linux Using Greybus Subsystem
50mHotplug of Non-discoverable Hardware: Status and Future Directions
45mPowering up "discoverable bus-attached" devices on DT-based platforms
36mIntroduction to HyperBus Memory Devices
40m10 Years of the Industrial I/O Kernel Subsystem
45mUSB Support in Zephyr OS