1. 06 Jul, 2018 1 commit
    • spiiroin's avatar
      [usb_moded] Add configfs support. JB#42083 · 79c7a763
      spiiroin authored
      Add custom Makefile for faster smoke-test rebuilds without spending time
      in configure, autotools, document generation and/or rolling rpm packages.
      
      Add multiple include protection to all header files.
      
      Move function prototypes away from header files that included in the
      development package.
      
      Mass rename functions to have a prefix giving context for the function.
      For the most part the prefix is derived from the name of the compilation
      module containing the function.
      
      Mass normalize indentation to four spaces in all source files.
      
      Augment author lists on each source file based on git committers.
      
      Remove "inline" attributes from not-really-inlineable functions.
      
      Remove .gitignore.
      
      Remove unused modules-android.c source file.
      
      Define _GNU_SOURCE for whole build rather than in individual files.
      
      Fix resource leaks here and there.
      
      Try to avoid hard-coding android usb paths.
      
      Add configfs backend for usb cadget configuration.
      
      Probe supported backends (configfs, android usb, or kmod) on usb-moded
      startup and make them mutually exclusive with each other.
      
      Allow configfs and android usb control structures some time to show up
      if usb-moded is started during device bootup.
      
      Refactor udev event listener to utilize a state machine. Simplifies
      book keeping and makes pc/charger detection heuristics easier to control.
      
      Refactor mode selection to utilize three interconnected mini state machines.
      Allows separating logically wanted mode from mode programmed to usb and
      mode exposed over D-Bus.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      79c7a763
  2. 05 Jun, 2018 3 commits
  3. 29 Mar, 2018 1 commit
  4. 28 Mar, 2018 7 commits
  5. 08 Mar, 2018 2 commits
  6. 01 Dec, 2017 2 commits
    • spiiroin's avatar
      [udev] Do not exit if cable state can't be determined · 22bcd9f4
      spiiroin authored
      If usb-moded exits when it can't deduce cable connect state, it will
      be restarted by systemd. As the usb-moded restarts are not going to
      change how the udev status looks like, this repeats until systemd
      moves the usb-moded service to failed state.
      
      Do not exit and assume no usb-cable is connected. In addition to not
      triggering restart spree, this has the additional benefit that the
      usb-moded dbus interface stays available and signaling not-connected
      state.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      22bcd9f4
    • spiiroin's avatar
      [udev] Suppress repetitive property warnings. Fixes JB#40394 · 0d5a10b7
      spiiroin authored
      Usb-moded expects to see POWER_SUPPLY_PRESENT and POWER_SUPPLY_TYPE
      properties defined for usb power-supply devices. When this is not
      the case, it emits warnings and applies various fallbacks. Since the
      properties get re-evaluated periodically, this also leads to the
      same warnings being repeated.
      
      Refactor the code so that in default verbosity the property warnings
      are emitted only during what looks like cable connect / disconnect.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      0d5a10b7
  7. 14 Nov, 2017 1 commit
  8. 17 Aug, 2017 3 commits
    • spiiroin's avatar
      [modesetting] Write dummy value to clear ffs function list. Fixes JB#39402 · e7536ebc
      spiiroin authored
      It seems that kernels in many if not all devices ignore writing of empty
      string to ffs function control file - the function list is left as it were
      and this can cause subtle issues on the next cable connect. On the other
      hand writing a non-existing "function" will clear the function list, but
      causes write error to be reported.
      
      Treat attempts to clear function list as a special case so that non-empty
      string gets written and the resulting write error is ignored under normal
      logging verbosity.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      e7536ebc
    • spiiroin's avatar
      [debug] Do diagnostic logging for each D-Bus signal broadcast · 3350e0b6
      spiiroin authored
      When debugging order and timing of issues related to several processes
      it is handy to have signals emitted by usb-moded in the journal along
      with the other related logging.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      3350e0b6
    • spiiroin's avatar
      [debug] Optionally include file/line/function info when logging to stderr · 3420f50a
      spiiroin authored
      When debugging usb-moded it is time consuming to find where the
      various debug messages originate from.
      
      When logging to stderr, prefix the messages with source code
      position info similar as gcc uses for reporting compilation
      issues. This allows browsing usb-moded code with jump to the
      next error functionality available in many text editors.
      
      Since the amount of information passed to logging functions
      is significantly increased, check whether the message would
      be emitted or not before evaluating formatting parameters etc.
      
      Also make variables relating to logging level, type, etc
      available only via accessor functions.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      3420f50a
  9. 11 Aug, 2017 1 commit
  10. 26 Apr, 2017 8 commits
  11. 24 Mar, 2017 3 commits
  12. 13 Mar, 2017 2 commits
    • spiiroin's avatar
      [doc] Document undocumented structures · 1e3378f6
      spiiroin authored
      Undocumented structures cause warnings during documentation generation.
      
      Add missing doxygen documentation comments for structures.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      1e3378f6
    • spiiroin's avatar
      [usb-moded] Use MEEGOLOCK features only when enabled. Fixes MER#1765 · 04e3a753
      spiiroin authored
      The is_in_user_state() is used unconditionally, but it is available only
      when --enable-meegodevlock option has been passed to configure. Also,
      the related "usb_moded-dsme.h" is included both unconditionally and from
      withing a #ifdef MEEGOLOCK block - which hides the configuration problem
      until build proceeds to linking phase.
      
      Make the call is_in_user_state() only if MEEGOLOCK is defined.
      
      Remove the extraneous "usb_moded-dsme.h" include to make such errors
      visible already in compilation stage due to missing prototypes.
      
      Also, make sure the "usb_moded-dsme.h" can't be included without
      warnings unless MEEGOLOCK is defined.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      04e3a753
  13. 14 Feb, 2017 3 commits
  14. 31 Jan, 2017 1 commit
  15. 07 Dec, 2016 1 commit
    • spiiroin's avatar
      [ssu] Use ssusysinfo instead of SSU D-Bus interface · 536e0e4f
      spiiroin authored
      During bootup usb-moded needs device name / model information before
      the system has reached a point where SSU daemon can be started. This
      can cause systemd deadlocks and/or timeouts as usb-moded waits for SSU
      daemon and the rest of the bootup is blocked until usb-moded reaches
      ready state.
      
      Use ssu-sysinfo C-library that can provide the device details required
      by usb-moded without using any IPC mechanisms.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      536e0e4f
  16. 07 Nov, 2016 1 commit
    • spiiroin's avatar
      [modules] Clear context pointer after dropping reference · f3a01678
      spiiroin authored
      Not explicitly initializing the pointer to null value makes the validity
      of the initial state subject to compiler/libc level implementation details.
      And not clearing the pointer after dropping the reference can lead to
      hard to debug issues if the potentially state pointer is used later on.
      
      Explicitly initialize the context to null value and set it back to null
      after dropping the reference.
      Signed-off-by: spiiroin's avatarSimo Piiroinen <simo.piiroinen@jollamobile.com>
      f3a01678