Integrete ISH kernel driver and ISH driver should provoide following interface to user
(1) Batch Mode----Get the hardware batch buffer size/count,Set the batch timeout value
(2) Wakeup/non-wakeup----checking if one sensor is wakeup instance or non-wakeup instance.For wakeup instance, when batch buffer is full or wait timeout, system must be woken up and receive batched sensor events.
(3) Timestamp ---- expose the sensor event timestamp to user space for sync
(4) physical sensors-----support exposing following physical sensors:Accelerometer,Gyroscope,Magnetic,Field,Pressure,Light,Proximity
(5) Advanced sensor----support exposing following advanced sensors:
Gravity,Linear Acceleration,Rotation Vector,Orientation,Game Rotation,Geomagentic Rotation,Step Detector,Step Counter,Terminal,Significant motion,Wakeup Gesture,Glance Gesture,Tilt,PanZoon,Lift and Look
(6)multiple sensor instance support
(7)private command support ---- support set/get path for private command set and response get, because some advanced sensor needs different special command to work properly.
(8)User defined sensor support--- exposing non-pre-defined sensors.
Because customer may add a new sensor in firmware, and hope sensor driver can expose it as a unknown sensor automatically, then application can use it directly without any code change.
Integrete ISH kernel driver and ISH driver should provoide following interface to user non-wakeup- ---checking if one sensor is wakeup instance or non-wakeup instance.For wakeup instance, when batch buffer is full or wait timeout, system must be woken up and receive batched sensor events. Accelerometer, Gyroscope, Magnetic, Field,Pressure, Light,Proximity Rotation Vector, Orientation, Game Rotation, Geomagentic Rotation,Step Detector,Step Counter, Terminal, Significant motion,Wakeup Gesture,Glance Gesture, Tilt,PanZoon, Lift and Look
(1) Batch Mode----Get the hardware batch buffer size/count,Set the batch timeout value
(2) Wakeup/
(3) Timestamp ---- expose the sensor event timestamp to user space for sync
(4) physical sensors-----support exposing following physical sensors:
(5) Advanced sensor----support exposing following advanced sensors:
Gravity,Linear Acceleration,
(6)multiple sensor instance support
(7)private command support ---- support set/get path for private command set and response get, because some advanced sensor needs different special command to work properly.
(8)User defined sensor support--- exposing non-pre-defined sensors.
Because customer may add a new sensor in firmware, and hope sensor driver can expose it as a unknown sensor automatically, then application can use it directly without any code change.
HW: Broxton-p
Upstream Schedule:
Basic Sensor Driver: 4.9
Advanced Sensor Driver: TBD