1. 11 4月, 2019 1 次提交
  2. 03 4月, 2019 3 次提交
  3. 29 3月, 2019 1 次提交
  4. 26 3月, 2019 2 次提交
  5. 22 3月, 2019 4 次提交
  6. 21 3月, 2019 2 次提交
  7. 20 3月, 2019 5 次提交
  8. 19 3月, 2019 7 次提交
  9. 02 3月, 2019 2 次提交
  10. 27 2月, 2019 2 次提交
    • B
      arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node · 5364a0b4
      Brian Norris 提交于
      Currently, we don't coordinate BT USB activity with our handling of the
      BT out-of-band wake pin, and instead just use gpio-keys. That causes
      problems because we have no way of distinguishing wake activity due to a
      BT device (e.g., mouse) vs. the BT controller (e.g., re-configuring wake
      mask before suspend). This can cause spurious wake events just because
      we, for instance, try to reconfigure the host controller's event mask
      before suspending.
      
      We can avoid these synchronization problems by handling the BT wake pin
      directly in the btusb driver -- for all activity up until BT controller
      suspend(), we simply listen to normal USB activity (e.g., to know the
      difference between device and host activity); once we're really ready to
      suspend the host controller, there should be no more host activity, and
      only *then* do we unmask the GPIO interrupt.
      
      This is already supported by btusb; we just need to describe the wake
      pin in the right node.
      
      We list 2 compatible properties, since both PID/VID pairs show up on
      Scarlet devices, and they're both essentially identical QCA6174A-based
      modules.
      
      Also note that the polarity was wrong before: Qualcomm implemented WAKE
      as active high, not active low. We only got away with this because
      gpio-keys always reconfigured us as bi-directional edge-triggered.
      
      Finally, we have an external pull-up and a level-shifter on this line
      (we didn't notice Qualcomm's polarity in the initial design), so we
      can't do pull-down. Switch to pull-none.
      Signed-off-by: NBrian Norris <briannorris@chromium.org>
      Reviewed-by: NMatthias Kaehlcke <mka@chromium.org>
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      5364a0b4
    • M
      arm64: dts: qcom: msm8998: Extend TZ reserved memory area · 6e533309
      Marc Gonzalez 提交于
      My console locks up as soon as Linux writes to [88800000,88f00000[
      AFAIU, that memory area is reserved for trustzone.
      
      Extend TZ reserved memory range, to prevent Linux from stepping on
      trustzone's toes.
      
      Cc: stable@vger.kernel.org # 4.20+
      Reviewed-by: NSibi Sankar <sibis@codeaurora.org>
      Fixes: c7833949 ("arm64: dts: qcom: msm8998: Add smem related nodes")
      Signed-off-by: NMarc Gonzalez <marc.w.gonzalez@free.fr>
      Signed-off-by: NAndy Gross <andy.gross@linaro.org>
      6e533309
  11. 22 2月, 2019 1 次提交
  12. 21 2月, 2019 1 次提交
  13. 19 2月, 2019 1 次提交
  14. 18 2月, 2019 6 次提交
  15. 16 2月, 2019 2 次提交
反馈
建议
客服 返回
顶部