EOSS-EU23-Introducing a New Zephyr Sensing Subsystem.pdf

1、#EMBEDDEDOSSUMMITHebo Hu,Ke HanIntel CorporationIntroducing a New Zephyr Sensing Subsystem Zephyr Sensing Subsystem Agenda Items Why do we need it?Background What is our goal?Motivation What is it?Introduction What can it do?Application How far did we go?Status How does it work?Demo What is next?Nex

2、t PlanZephyr Sensors TodayTypical Zephyr Sensor Usages device tree config sensor fetching sensor triggering sensor attribute sensor calibration sensor processing 140 device drivers 900 commitsImprovement area:sensor applications are directly interacting with sensor device drivers for all sensor oper

3、ations,there is a lack of high-level abstraction,general function management,multi-client arbitration,etc.in Zephyr Sensor solutionBackgroundSensor Device DriverSensor Device DriverSensor Device DriverSensor ApplicationSensor ApplicationSensor ApplicationMotivationTake Zephyr Sensor Solution to Next

4、 LevelPlan:introduce a new sensing subsystem/framework to support Sensor high level abstraction General function management Multi-client arbitration Sensor topology and scheduling Sensor fusion and processing Sensor timestamping Sensor batching And more Furthermore:With additional components,new Sen

5、sing Subsystem shall be able to serve as sensor framework in sensor hub firmware,to support OS sensing stack(Windows*,Chrome*,Android*,Linux*)and CHRE*.Sensor Device DriverSensor Device DriverSensor Device DriverSensor ApplicationSensor ApplicationSensor ApplicationNew Zephyr Sensing Subsystem*Other

6、 names and brands may be claimed as the property of othersIntroductionUser Space(if configured)Kernel SpacePlatform HWSensor Driver APISensorAPI(single client)I2CSPIUARTGPIO.GyroAccMagALSZephyr Low Level APIsIPCSensing Subsystem API（multiple clients support）Zephyr High Level APIsZephyr existing sens