1. 27 7月, 2021 1 次提交
    • M
      spi: imx: mx51-ecspi: Fix low-speed CONFIGREG delay calculation · 53ca18ac
      Marek Vasut 提交于
      The spi_imx->spi_bus_clk may be uninitialized and thus also zero in
      mx51_ecspi_prepare_message(), which would lead to division by zero
      in kernel. Since bitbang .setup_transfer callback which initializes
      the spi_imx->spi_bus_clk is called after bitbang prepare_message
      callback, iterate over all the transfers in spi_message, find the
      one with lowest bus frequency, and use that bus frequency for the
      delay calculation.
      
      Note that it is not possible to move this CONFIGREG delay back into
      the .setup_transfer callback, because that is invoked too late, after
      the GPIO chipselects were already configured.
      
      Fixes: 135cbd37 ("spi: imx: mx51-ecspi: Reinstate low-speed CONFIGREG delay")
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Cc: Mark Brown <broonie@kernel.org>
      Link: https://lore.kernel.org/r/20210726100102.5188-1-marex@denx.deSigned-off-by: NMark Brown <broonie@kernel.org>
      53ca18ac
  2. 22 7月, 2021 3 次提交
  3. 20 7月, 2021 1 次提交
  4. 19 7月, 2021 1 次提交
    • M
      spi: cadence: Correct initialisation of runtime PM again · 56912da7
      Marek Vasut 提交于
      The original implementation of RPM handling in probe() was mostly
      correct, except it failed to call pm_runtime_get_*() to activate the
      hardware. The subsequent fix, 734882a8 ("spi: cadence: Correct
      initialisation of runtime PM"), breaks the implementation further,
      to the point where the system using this hard IP on ZynqMP hangs on
      boot, because it accesses hardware which is gated off.
      
      Undo 734882a8 ("spi: cadence: Correct initialisation of runtime
      PM") and instead add missing pm_runtime_get_noresume() and move the
      RPM disabling all the way to the end of probe(). That makes ZynqMP
      not hang on boot yet again.
      
      Fixes: 734882a8 ("spi: cadence: Correct initialisation of runtime PM")
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: Charles Keepax <ckeepax@opensource.cirrus.com>
      Cc: Mark Brown <broonie@kernel.org>
      Link: https://lore.kernel.org/r/20210716182133.218640-1-marex@denx.deSigned-off-by: NMark Brown <broonie@kernel.org>
      56912da7
  5. 17 7月, 2021 1 次提交
    • A
      spi: cadence-quadspi: Disable Auto-HW polling · 9cb2ff11
      Apurva Nandan 提交于
      cadence-quadspi has a builtin Auto-HW polling funtionality using which
      it keep tracks of completion of write operations. When Auto-HW polling
      is enabled, it automatically initiates status register read operation,
      until the flash clears its busy bit.
      
      cadence-quadspi controller doesn't allow an address phase when
      auto-polling the busy bit on the status register. Unlike SPI NOR
      flashes, SPI NAND flashes do require the address of status register
      when polling the busy bit using the read register operation. As
      Auto-HW polling is enabled by default, cadence-quadspi returns a
      timeout for every write operation after an indefinite amount of
      polling on SPI NAND flashes.
      
      Disable Auto-HW polling completely as the spi-nor core, spinand core,
      etc. take care of polling the busy bit on their own.
      Signed-off-by: NApurva Nandan <a-nandan@ti.com>
      Link: https://lore.kernel.org/r/20210713125743.1540-2-a-nandan@ti.comSigned-off-by: NMark Brown <broonie@kernel.org>
      9cb2ff11
  6. 16 7月, 2021 3 次提交
  7. 14 7月, 2021 1 次提交
  8. 12 7月, 2021 2 次提交
  9. 08 7月, 2021 1 次提交
  10. 07 7月, 2021 1 次提交
  11. 30 6月, 2021 1 次提交
  12. 25 6月, 2021 3 次提交
  13. 23 6月, 2021 9 次提交
  14. 22 6月, 2021 2 次提交
  15. 17 6月, 2021 2 次提交
  16. 15 6月, 2021 2 次提交
  17. 14 6月, 2021 3 次提交
  18. 09 6月, 2021 1 次提交
  19. 07 6月, 2021 1 次提交
  20. 04 6月, 2021 1 次提交