1. 14 Sep, 2020 1 commit
  2. 20 Nov, 2018 1 commit
  3. 19 Sep, 2018 5 commits
  4. 16 Mar, 2018 1 commit
  5. 28 Feb, 2018 1 commit
    • spiiroin's avatar
      [datapipe] Unify naming. Contributes to JB#22475 · 5fadb870
      spiiroin authored
      Use "datapipe_"  prefix for all functions:
       datapipe_add_filter            <- append_filter_to_datapipe
       datapipe_add_input_trigger     <- append_input_trigger_to_datapipe
       datapipe_add_output_trigger    <- append_output_trigger_to_datapipe
       datapipe_exec_filters          <- execute_datapipe_filters
       datapipe_exec_full             <- execute_datapipe
       datapipe_exec_input_triggers   <- execute_datapipe_input_triggers
       datapipe_exec_output_triggers  <- execute_datapipe_output_triggers
       datapipe_free                  <- free_datapipe
       datapipe_init                  <- setup_datapipe
       datapipe_remove_filter         <- remove_filter_from_datapipe
       datapipe_remove_input_trigger  <- remove_input_trigger_from_datapipe
       datapipe_remove_output_trigger <- remove_output_trigger_from_datapipe
      Datapipes that are used for solely for requesting state changes (i.e. do not
      themselves have a state) have a verb in the name:
       display_state_request_pipe          <- display_state_req_pipe
       led_pattern_activate_pipe           (no change)
       led_pattern_deactivate_pipe         (no change)
       tklock_request_pipe                 <- tk_lock_pipe
      Datapipes that are used solely process input events without having a
      persistent state have "event" in the name:
       heartbeat_event_pipe                <- heartbeat_pipe
       ignore_incoming_call_event_pipe     <- ignore_incoming_call_pipe
       inactivity_event_pipe               <- device_inactive_event_pipe
       keypress_event_pipe                 <- keypress_pipe
       resume_detected_event_pipe          <- device_resumed_pipe
       touchscreen_event_pipe              <- touchscreen_pipe
       user_activity_event_pipe            <- user_activity_pipe
      Datapipes dealing with brightness have "brightness" included in the name:
       display_brightness_pipe             (no change)
       key_backlight_brightness_pipe       <- key_backlight_pipe
       led_brightness_pipe                 (no change)
       lpm_brightness_pipe                 (no change)
      Datapipes dealing with sensors have "sensor" in name and the one holding
      unfiltered data is called "actual":
       lid_sensor_actual_pipe              <- lid_cover_sensor_pipe
       lid_sensor_filtered_pipe            <- lid_cover_policy_pipe
       lid_sensor_is_working_pipe          (no change)
       light_sensor_actual_pipe            <- ambient_light_sensor_pipe
       light_sensor_filtered_pipe          <- ambient_light_level_pipe
       light_sensor_poll_request_pipe      <- ambient_light_poll_pipe
       orientation_sensor_actual_pipe      <- orientation_sensor_pipe
       proximity_sensor_actual_pipe        <- proximity_sensor_pipe
      Datapipes that have enumerated state reflect the enumeration type in
      datapipe name:
       alarm_ui_state_pipe                 (no change)
       audio_route_pipe                    (no change)
       battery_status_pipe                 (no change)
       bluez_service_state_pipe            <- bluez_available_pipe
       call_state_pipe                     (no change)
       call_type_pipe                      (no change)
       camera_button_state_pipe            <- camera_button_pipe
       charger_state_pipe                  (no change)
       compositor_service_state_pipe       <- compositor_available_pipe
       devicelock_service_state_pipe       <- devicelock_available_pipe
       devicelock_state_pipe               <- device_lock_state_pipe
       display_state_curr_pipe             <- display_state_pipe
       display_state_next_pipe             (no change)
       dsme_service_state_pipe             <- dsme_available_pipe
       jack_sense_state_pipe               <- jack_sense_pipe
       keyboard_available_state_pipe       <- keyboard_available_pipe
       keyboard_slide_state_pipe           <- keyboard_slide_pipe
       lens_cover_state_pipe               <- lens_cover_pipe
       lipstick_service_state_pipe         <- lipstick_available_pipe
       lockkey_state_pipe                  <- lockkey_pipe
       ngfd_service_state_pipe             <- ngfd_available_pipe
       submode_pipe                        (no change)
       system_state_pipe                   (no change)
       thermal_state_pipe                  (no change)
       uiexception_type_pipe               <- exception_state_pipe
       usb_cable_state_pipe                <- usb_cable_pipe
       usbmoded_service_state_pipe         <- usbmoded_available_pipe
      Datapipes that have boolean state should answer an
      "is" question:
       device_inactive_pipe                <- device_inactive_state_pipe
       interaction_expected_pipe           (no change)
       keypad_grab_active_pipe             (no change)
       keypad_grab_wanted_pipe             (no change)
       master_radio_enabled_pipe           <- master_radio_pipe
       music_playback_ongoing_pipe         <- music_playback_pipe
       osupdate_running_pipe               <- update_mode_pipe
       packagekit_locked_pipe              (no change)
       power_saving_mode_active_pipe       <- power_saving_mode_pipe
       proximity_blanked_pipe              <- proximity_blank_pipe
       shutting_down_pipe                  (no change)
       touch_detected_pipe                 (no change)
       touch_grab_active_pipe              (no change)
       touch_grab_wanted_pipe              (no change)
      Datapipes that have integer state should answer
      and "what is" question:
       battery_level_pipe                  (no change)
       inactivity_delay_pipe               <- inactivity_timeout_pipe
      Rename datapipe related callback functions and variables similarly as what
      was done to datapipes.
      Define submode bitmasks as submode_t enumeration instead of using
      gint type and preprocessor constants. Change the value naming from
      MCE_xxx_SUBMODE to MCE_SUBMODE_xxx.
      Change call_type_t enumeration value naming from xxx_CALL to
      Change system_state_t enumeration value naming from MCE_STATE_xxx
      to MCE_SYSTEM_STATE_xxx.
      Fix setting up of power_saving_mode_active_pipe, master_radio_enabled_pipe
      and lens_cover_state_pipe so that initial values of appropriate type are
      Switch lockkey_state_pipe value from gboolean to key_state_t type.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
  6. 02 Jun, 2017 1 commit
    • spiiroin's avatar
      [inactivity] Skip activity renew instead of switching to inactivity · 5c3916fe
      spiiroin authored
      Datapipe filter callback functions can only modify the value that datapipe
      ends up having and can't be used to skip calling of notification functions.
      In case of inactivity processing this means that when filter function does
      not allow extending of "user activity" period, it actually immediately
      terminates the period.
      Instead of having a single inactivity datapipe with filter callback, use two
      separate "event" and "state" datapipes chained so that events can be
      propagated from event to state datapipe or ignored depending on whether the
      activity change is allowed or not.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
  7. 12 May, 2017 1 commit
  8. 18 Jan, 2017 1 commit
  9. 31 Mar, 2016 4 commits
    • spiiroin's avatar
      [settings] Remove gconf references from code. Fixes MER#1554 · d8f66013
      spiiroin authored
      Rename functions, variables and structure members so that only functions
      dealing directly with gconf api (implemented in builtin-gconf module)
      contain gconf in name.
      When local naming convention permits: Use _setting_cb postfix for
      naming change notification callback functions and _setting_id for
      naming notification tracking ids.
      When applicable: Move tracking ids so that they are next to the variable
      that is used for caching the setting value and remove repetitive and
      uninformative Doxygen comments.
      No functional changes.
    • spiiroin's avatar
      [settings] Use mce-setting module. MER#1554 · 07dd89fe
      spiiroin authored
      Change all mce-gconf.[ch] references to mce-setting.[ch].
      No functional changes.
    • spiiroin's avatar
      [settings] Remove gconf references from interface function names. MER#1554 · 9c04e702
      spiiroin authored
      Use mce_setting prefix instead of mce_gconf.
      No functional changes.
    • spiiroin's avatar
      [settings] Remove gconf references from key names. MER#1554 · eec0197e
      spiiroin authored
      Use MCE_SETTING prefix for key name macros and MCE_DEFAULT prefix for
      key default values.
      Also fix changed headers so that:
      - Reserved names are not used for multiple inclusion protection
      - Unneeded C++ preprocess hacks are removed
      - Indentation of macros is unified
      No functional changes.
  10. 24 Apr, 2015 1 commit
    • spiiroin's avatar
      Add setting for ignoring lid/cover sensor · 1909bbaf
      spiiroin authored
      If mce find that a device has lid/cover sensor, it is used as a very
      high priority input for display blanking policy. It might be desirable
      to stop this from happening if for example:
      - user does not like the feature
      - mce input device probing produces a false match
      - the sensor is unreliable and makes using the device difficult
      - we want to keep the display on during sensor testing activities
      Add disable/enable setting for using lid/cover sensor.
      By default the setting is enabled, but can be changed for example by
      installing hw specific mce configuration files or from command line
        mcetool --set-lid-sensor-mode=<enabled|disabled>
      The setting persists over mce/device restarts.
      [mce] Add setting for ignoring lid/cover sensor. Fixes JB#28108
  11. 14 Nov, 2013 3 commits
  12. 13 Nov, 2013 2 commits
  13. 28 Oct, 2013 1 commit
    • spiiroin's avatar
      Provide visibility to cached display state polling · 44bb81c4
      spiiroin authored
      The transient power up/down states do not show up in datapipe
      output triggers, but code that reads directly from datapipe
      might see them and cause problems. These changes make it easier
      to find the places where this happens.
  14. 11 Oct, 2013 2 commits
  15. 04 Oct, 2013 1 commit