Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sensing Subsystem Upstream PR1 #55389

Merged
merged 8 commits into from Jun 17, 2023

Commits on Jun 9, 2023

  1. sensing: Adding Sensing Subsystem API

    This API introduced a new sensing subsystem, which is a high level
    sensor framework inside the OS user space service layer.
    It's a framework focus on sensor fusion, clients arbitration, sampling,
    timing, scheduling and sensor based power management.
    
    It's key concepts including physical sensor and virtual sensor objects,
    and a scheduling framework reflects sensor objects' reporting relationship.
    Physical sensors not depends on any other sensor objects for input, and
    will directly interact with existing zephyr sensor device drivers.
    Virtual sensors rely on other sensor objects (physical or virtual) as
    report inputs.
    
    The sensing subsystem relies on existing zephyr sensor device APIs or V2
    zephyr sensor device APIs (zephyrproject-rtos#44098).
    
    So it can leverage current existing zephyr sensor device drivers (100+).
    And it's configurable, so, for some low cost IoT devices, may not need an
    advanced sensor framework, but just need access some simple sensor
    devices,can not configure and build this sensor subsystem, but just use
    the exiting zephyr sensor device APIs to save memory resources.
    
    Since the sensing subsystem is separated from device driver layer or
    kernel space and could support various customizations and sensor
    algorithms in user space with virtual sensor concepts. The existing
    sensor device driver can focus on low layer device side works, can keep
    simple as much as possible, just provide device HW abstraction and
    operations etc. This is very good for system stability.
    
    The sensing subsystem is decoupled with any sensor expose/transfer
    protocols, the target is to support various up-layer frameworks and
    Applications with different sensor expose/transfer protocols,
    such as CHRE, HID sensors Applications, MQTT sensor Applications
    according different products requirements. Or even support multiple
    Applications with different up-layer sensor protocols at the same time
    with it's multiple clients support design. For example can support CHRE
    and other normal zephyr sensor application (can use HID etc) at
    the same time.
    
    Signed-off-by: Hebo Hu <hebo.hu@intel.com>
    Signed-off-by: Guangfu Hu <guangfu.hu@intel.com>
    huhebo authored and ghu0510 committed Jun 9, 2023
    Copy the full SHA
    38a0aa3 View commit details
    Browse the repository at this point in the history
  2. doc: Add documents for Sensing Subsystem

    Add documents for sensing subsystem.
    
    Signed-off-by: Hebo Hu <hebo.hu@intel.com>
    huhebo authored and ghu0510 committed Jun 9, 2023
    Copy the full SHA
    35410e8 View commit details
    Browse the repository at this point in the history
  3. sensing: add Sensing Subsystem skeleton

    Add Sensing Subsystem skeleton.
    
    Signed-off-by: Guangfu Hu <guangfu.hu@intel.com>
    Signed-off-by: Zhang Lixu <lixu.zhang@intel.com>
    lixuzha authored and ghu0510 committed Jun 9, 2023
    Copy the full SHA
    f124e0a View commit details
    Browse the repository at this point in the history
  4. sensing: phy_3d_sensor: add phy_3d_sensor skeleton

    Add the sensor phy_3d_sensor skeleton in Sensing Subsystem.
    
    Signed-off-by: Zhang Lixu <lixu.zhang@intel.com>
    lixuzha authored and ghu0510 committed Jun 9, 2023
    Copy the full SHA
    0af3a59 View commit details
    Browse the repository at this point in the history
  5. sensing: initial sensor list and enumerate each sensor

    Implement sensing_init():
    	1) create sensors from device tree
    	2) sequence sensors following node dependency ordering rule generated by
    	   Zephyr DTS
    	3) initial each sensor, includes:
    		a) creating sensor connection between reporter and client,
    		b) calling sensor init callback,
    		c) setting sensor state
    Implement sensing_open_sensor():
    	1) malloc connection from reporter to application
    	2) bind connection
    Implement sensing_close_sensr():
    	1) unbind connection
    	2) free connection from reporter to application
    Implement sensing_set_config():
    	1) call set_interval
    	2) cann set_sensitivity
    Implement sensing_get_config():
    	1) call get_interval
    	2) call get_sensitivity
    
    Signed-off-by: Guangfu Hu <guangfu.hu@intel.com>
    ghu0510 committed Jun 9, 2023
    Copy the full SHA
    d00b0aa View commit details
    Browse the repository at this point in the history
  6. samples: sensing: add a simple sensing subsystem app

    Add a simple sensing subsystem application.
    
    Signed-off-by: Guangfu Hu <guangfu.hu@intel.com>
    ghu0510 committed Jun 9, 2023
    Copy the full SHA
    a372944 View commit details
    Browse the repository at this point in the history
  7. MAINTAINERS: Add maintainer and collaborator for Sensing Subsystem

    Add lixuzha, ghu0510, qianruh as maintainer and collaborators for
    the Sensing Subsystem.
    
    Signed-off-by: Zhang Lixu <lixu.zhang@intel.com>
    lixuzha authored and ghu0510 committed Jun 9, 2023
    Copy the full SHA
    58ed821 View commit details
    Browse the repository at this point in the history
  8. CODEOWNERS: Add code owners for Sensing Subsystem

    Add lixuzha, ghu0510, qianruh for the Sensor Subsystem.
    
    Signed-off-by: Zhang Lixu <lixu.zhang@intel.com>
    lixuzha authored and ghu0510 committed Jun 9, 2023
    Copy the full SHA
    189d771 View commit details
    Browse the repository at this point in the history