1. 17 11月, 2018 1 次提交
  2. 14 11月, 2018 3 次提交
  3. 05 11月, 2018 1 次提交
    • J
      spi: pxa2xx: Remove LPSS private register restoring during resume · b53548f9
      Jarkko Nikula 提交于
      Intel LPSS private register restoring in spi-pxa2xx.c: pxa2xx_spi_resume()
      was added before there was no any other code restoring them. This was
      changed after following commits for previous and current LPSS platforms:
      
      c78b0830 ("ACPI / LPSS: custom power domain for LPSS")
      41a3da2b ("mfd: intel-lpss: Save register context on suspend")
      
      However there is one caveat: There is no LPSS private register context
      save/restore for the Intel Lynxpoint in the Linux kernel code.
      
      I did some debugging on one Lynxpoint based device I have and on it the
      LPSS register context is not lost over suspend/resume cycle (s2idle).
      Which happens for instance on Intel Braswell. I'm speculating but I guess
      either firmware does it or the LPSS is kept always on Lynxpoint.
      
      Given that we haven't needed to implement Lynxpoint LPSS I2C or UART
      private register context save/restore over four years time I think we are
      safe to remove this LPSS private register restoring during resume here.
      Signed-off-by: NJarkko Nikula <jarkko.nikula@linux.intel.com>
      Acked-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      b53548f9
  4. 11 10月, 2018 2 次提交
  5. 04 10月, 2018 1 次提交
  6. 18 9月, 2018 1 次提交
  7. 05 9月, 2018 1 次提交
  8. 28 6月, 2018 1 次提交
  9. 04 5月, 2018 1 次提交
  10. 18 4月, 2018 4 次提交
  11. 07 3月, 2018 1 次提交
  12. 12 2月, 2018 2 次提交
  13. 23 12月, 2017 1 次提交
  14. 21 12月, 2017 1 次提交
  15. 04 8月, 2017 1 次提交
  16. 28 7月, 2017 2 次提交
  17. 17 7月, 2017 1 次提交
  18. 07 6月, 2017 1 次提交
  19. 24 1月, 2017 1 次提交
  20. 19 1月, 2017 1 次提交
  21. 18 1月, 2017 1 次提交
  22. 05 1月, 2017 1 次提交
  23. 30 9月, 2016 1 次提交
  24. 27 9月, 2016 1 次提交
    • M
      spi: pxa2xx: Add support for GPIO descriptor chip selects · 99f499cd
      Mika Westerberg 提交于
      The driver uses custom chip_info coming from platform data for chip selects
      implemented as GPIOs. If the system lacks board files setting up the
      platform data, it is not possible to use GPIOs as chip selects.
      
      This adds support for GPIO descriptors so that regardless of the underlying
      firmware interface (DT, ACPI or platform data) the driver can request GPIOs
      used as chip selects and configure them accordingly.
      
      The custom chip_info GPIO support is still left there to make sure the
      existing systems keep working as expected.
      Signed-off-by: NMika Westerberg <mika.westerberg@linux.intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      99f499cd
  25. 13 9月, 2016 4 次提交
  26. 07 7月, 2016 1 次提交
  27. 04 7月, 2016 1 次提交
  28. 22 6月, 2016 2 次提交