1. 26 Jun, 2018 2 commits
  2. 29 May, 2018 1 commit
    • spiiroin's avatar
      [sensormanager] Add plugin availability config and D-Bus queries. JB#41369 · 8cf47d1f
      spiiroin authored
      Allow disabling / enabling sensors plugins via config entries like:
      
        [available]
        proximitysensor=True
        magnetometersensor=False
        lidsensor=Feature_CoverSensor
        orientationsensor=Feature_GyroSensor|Feature_AccelerationSensor
      
      Where:
      - "True" means that loading of the sensor plugin is made available
        via D-Bus interface and can be loaded.
      - "False" means the plugin will not be loaded and sensor is not
        made available via D-Bus
      - "Feature_*" means that sensor availability is checked from hw
        settings. If sensorfwd is compiled without ssu-sysinfo support
        these will be treated similarly to "True".
      - "" (or plugin that does not have config entry) is taken as "True",
        but a warning is logged in case of sensor plugins.
      
      If a plugin that is enabled in configuration fails to load, it is
      marked as not available until sensorfwd restart.
      
      Add new D-Bus method calls:
      - availablePlugins() lists all available plugins
      - availableSensorPlugins() lists available sensor plugins (which,
        when loaded, make new sensor objects and interfaces available)
      - pluginAvailable(name) can be used to check whether a named plugin
        is installed and available
      
      Package default sensor availability configuration file that disables
      all sensors except those that can be evaluated based on the hw
      settings configuration.
      
      Add example of device specific configuration file - these should be
      installed from hw adaptation packages and can override the defaults.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      8cf47d1f
  3. 24 May, 2018 1 commit
    • spiiroin's avatar
      [config] Process config.d files in alnum order · 4a04b3ed
      spiiroin authored
      Each configuration file is kept in separate QSettings object and lookup
      for values is done in load order - which is reverse from convention
      where 10-something.conf can be overridden with 20-something-else.conf.
      
      Change evaluation so that latter files can override earlier ones under
      assumption that so far there have been no devices that would actually
      employ more than one config.d file and thus glitches are unlikely.
      
      Also merge data from all settings files into a single QSettings object
      i.e. trade a bit more complex startup for simpler lookups during runtime.
      
      The primary config file, if specified, still overrides any settings made
      from config.d files.
      
      Rename 90-sensord-default.conf to 10-sensord-default.conf so that it
      still is 10 points up from the minimum priority.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      4a04b3ed
  4. 18 Feb, 2018 1 commit
  5. 06 Aug, 2017 1 commit
  6. 29 Dec, 2016 1 commit
  7. 11 Nov, 2016 1 commit
  8. 08 Jul, 2015 1 commit
  9. 08 May, 2015 1 commit
  10. 13 Apr, 2015 1 commit
    • lpotter's avatar
      [sensorfw] get compass working Fixes MER#822 · 43b9d557
      lpotter authored
      * change magcalibration chain expected data type to
      CalibratedMagneticFieldData
      
      * add MagCoordinateAlignFilter to remap mag data points when needed
      
      * invalidate the hybris adaptor if no sensor is dynamically found.
      
      * if orientationadaptor (calibrated compass) is valid use it, otherwise
      use sensorfw for calibration and compass routines.
      
      This helps for hybris based systems, when virtual sensors are not
      present. It keeps the default hybris configuration file usable.
      43b9d557
  11. 11 Mar, 2015 1 commit
  12. 12 Jan, 2015 1 commit
  13. 26 Sep, 2013 1 commit
  14. 24 Sep, 2013 1 commit
  15. 21 Aug, 2013 1 commit
  16. 21 Jul, 2013 1 commit
  17. 09 Feb, 2013 4 commits
  18. 08 Feb, 2013 3 commits
  19. 13 Apr, 2011 2 commits
  20. 15 Mar, 2011 1 commit
  21. 10 Mar, 2011 1 commit
  22. 09 Mar, 2011 2 commits
  23. 08 Mar, 2011 1 commit
  24. 28 Feb, 2011 1 commit
  25. 25 Feb, 2011 1 commit
  26. 14 Feb, 2011 1 commit
  27. 11 Feb, 2011 2 commits
  28. 10 Feb, 2011 1 commit
  29. 09 Feb, 2011 3 commits