How to Contribute a Zephyr Sensor Driver
summary
Step-by-step checklist for a Zephyr sensor driver: implement a device tree binding with documented defaults, add Kconfig that uses the auto-generated DT exists flags, instantiate per-instance config/data with the sensor device DT inst Define wrapper, implement the user API (required fetch and get now; prepare for the experimental read and decode + rtio), add the node to the sensor driver build test, exercise with sensor shell, fix CI and meet merge rules (two approvals, one assignee approval, two business days, merge window).
AI-written summary · about
chapters (10)
- 0:00Zephyr sensor driver intro
- 1:29Key components
- 10:25Device tree bindings
- 16:35Runtime sensor API
- 23:45Multiple sensor instances
- 30:22Testing driver
- 38:02Contribution process
- 42:01Common mistakes
- 46:36Merge criteria
- 50:34Community collaboration
related talks
23mA Dive into Zephyr Device Driver Model
31mA Zephyr User Story- 23mA Dive into Zephyr Device Driver Model
40mHow to extract a bare metal flavor of code out of Zephyr to use in RTOS?
46mDevice Tree in Zephyr Project
33mImproving System Configuration for Zephyr and Beyond
27mIntroducing a New Zephyr Sensing Subsystem
44mConfigure Zephyr: Kconfigs and Devicetree in Simple Words