1. 28 Mar, 2022 4 commits
  2. 27 Mar, 2022 1 commit
  3. 25 Mar, 2022 1 commit
  4. 23 Mar, 2022 2 commits
  5. 17 Mar, 2022 8 commits
  6. 16 Mar, 2022 4 commits
    • Raghavendar rao l's avatar
      msm: ipa: Add support for IPA_v5_2 version · 27d02083
      Raghavendar rao l authored
      Added IPA-5.2 version support in header files.
      Change-Id: I47f2ab4205eeb6875d755152ff7153c5256bdf93
      Signed-off-by: default avatarRaghavendar rao l <quic_rlomte@quicinc.com>
    • Sai Chaitanya Kaveti's avatar
      msm: mhi_dev: Using channel mutex lock for channel specific lists · f62c2004
      Sai Chaitanya Kaveti authored
      Using channel mutex lock while accessing channel specific lists,
      event_req_buffers and flush_event_req_buffers. This will avoid any
      synchronization issues for these lists. Previously two different mutex
      locks, global MHI lock and channel lock are used while accessing these
      Removing MHI spin lock while accessing the above lists in
      mhi_dev_process_reset_cmd, mhi_dev_queue_transfer_completion and
      mhi_dev_flush_transfer_completion_events APIs as they are already
      protected by channel mutex lock obtained from the APIs that are
      calling these three APIs.
      Removing MHI spin lock in mhi_dev_event_msi_cb and adding channel mutex
      lock. In other instances where these lists are accessed they are already
      protected by channel mutex lock.
      Change-Id: I58b673be452a942ff946e07f17c96a0715805621
      Signed-off-by: default avatarSai Chaitanya Kaveti <quic_skaveti@quicinc.com>
    • Sai Chaitanya Kaveti's avatar
      msm: mhi_dev: Avoiding freeing of ereq memory in reset · 77221bae
      Sai Chaitanya Kaveti authored
      With the commit <1528bbe6
      > ("msm: mhi_dev: Keeping event req
      memory without clearing in close channel"), we are avoiding freeing
      of ereq memory in close channel API. New memory is not created again
      as part of start/open channel since it is not released while closing
      the channel. Idea is to hold the allocated memory and avoid
      reallocating every time.
      But during the reset command we are freeing some of the ereqs which we
      need to hold without releasing.
      This change avoids freeing of ereq memory as part of reset channel
      command and adds the ereqs to the event_req_buffers list. This ensures
      that the lists, event_req_buffers and flush_event_req_buffers are
      updated with valid ereqs.
      Change-Id: Ie29962f2bc8ef5a0c193d13a13118ae9b6044c0b
      Signed-off-by: default avatarSai Chaitanya Kaveti <quic_skaveti@quicinc.com>
    • Yuanfang Zhang's avatar
      byte-cntr: check pcie channel status before closing it · 224fd98c
      Yuanfang Zhang authored
      Check pcie channel status before call the close channel API, only
      closed it when it in open state.
      Change-Id: Ib3bee9575edfae0cc907baee4956d6e3a6c78d61
      Signed-off-by: default avatarYuanfang Zhang <quic_yuanfang@quicinc.com>
  7. 14 Mar, 2022 2 commits
    • Sai Chaitanya Kaveti's avatar
      msm: mhi_dev: Avoiding ereq memory allocation in start · 6bf118c8
      Sai Chaitanya Kaveti authored
      Start channel commands from MHI Host are given for all the set of valid
      channels during the initialization itself. Previously we are allocating
      ereq memory as part of start channel command. But, many of these channels
      may not be opened by the clients and the ereq memory allocated is not
      useful here.
      Here avoiding ereq memory allocation during start channel command and
      allocating memory only as part of open channel call by the clients. This
      will reduce the overall memory usage and avoid the memory allocation
      Change-Id: I60eccd1d17c60e1108820e1532f2ae385455f336
      Signed-off-by: default avatarSai Chaitanya Kaveti <quic_skaveti@quicinc.com>
    • Fenglin Wu's avatar
      input: qcom-hv-haptics: config open-loop drive when hBoost is enabled · b3a8a1b1
      Fenglin Wu authored
      With commit 8c194abb
       ("input: qcom-hv-haptics: delay hBoost turning
      off"), the hBoost would be kept as enabled in the 2 seconds after stopping
      play. If a new play is triggered in that 2 seconds, the hBoost will be
      considered as working in open-loop mode so configure haptics open-loop
      drive in such case.
      Change-Id: Ibfa533f23a52bd609e2a8564f859ca8835a8fd67
      Signed-off-by: default avatarFenglin Wu <quic_fenglinw@quicinc.com>
  8. 12 Mar, 2022 1 commit
  9. 10 Mar, 2022 4 commits
  10. 09 Mar, 2022 4 commits
  11. 08 Mar, 2022 3 commits
  12. 07 Mar, 2022 3 commits
  13. 05 Mar, 2022 2 commits
  14. 04 Mar, 2022 1 commit