Keynote: How Zephyr Enables Industry Collaboration
summary
Two and a half years ago Google switched embedded controller to Zephyr and now ships Chromebooks using Zephyr on the EC; unit tests jump from roughly 30% to over 90%. A concrete RFC and MVP for a battery fuel gauge API upstreamed lets Intel Microsoft Cirrus Logic and independent contributors add drivers and a charger API. Work also lands on a sensing subsystem, USB PD sync/source modes, and hardware tools like the Twinkie V2 USB power delivery analyzer and a Chameleon display emulator.
AI-written summary · about
chapters (7)
- 0:00Zephyr at Google
- 1:25First contribution & collaboration
- 3:08Battery API development
- 5:55Sensor subsystem work
- 8:06Other Google collaborations
- 9:11Zephyr in Chromebooks
- 11:39How to contribute
related talks
16mHow Zephyr is eating the (embedded) software world
13mKeynote: Zephyr is Not a Product!
33mSponsored Session: Why NXP is Doubling Down on Zephyr Project
33mSponsored Session: Why NXP is Doubling Down on Zephyr Project
40mBof: Zephyr Community in Japan: From Hobbyist To Automotive, Roboti...
40mBoF: Zephyr: Meet the Maintainers- 13mKeynote: Zephyr is Not a Product!
39mBoF: Meet the Zephyr Community