1. 22 10月, 2015 1 次提交
    • N
      spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message · 468a3208
      Neil Armstrong 提交于
      Since the "Switch driver to use transfer_one" change, the cs_change
      behavior has changed and a channel chip select can still be
      asserted when changing channel from a previous last transfer in a
      message having the cs_change attribute.
      
      Since there is no sense having multiple chip select being asserted at the
      same time, disable all the remaining forced chip selects in a the
      prepare_message called right before a spi_transfer_one_message call.
      It ignores the current channel configuration in order to keep the
      possibility to leave the chip select asserted between messages.
      
      It fixes this bug on a DM8168 SoC ES2.1 Soc and an OMAP4 ES2.1 SoC.
      It was hanging all the other channels transfers when a CHCONF_FORCE
      is present on the wrong channel.
      
      Fixes: b28cb941 ("spi: omap2-mcspi: Switch driver to use transfer_one")
      Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>
      Reviewed-by: NMichael Welling <mwelling@ieee.org>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      468a3208
  2. 25 7月, 2015 1 次提交
  3. 25 5月, 2015 4 次提交
  4. 13 5月, 2015 1 次提交
  5. 09 5月, 2015 1 次提交
  6. 08 5月, 2015 1 次提交
  7. 24 4月, 2015 1 次提交
  8. 22 12月, 2014 1 次提交
  9. 20 10月, 2014 1 次提交
  10. 12 8月, 2014 1 次提交
  11. 04 7月, 2014 1 次提交
    • M
      spi: omap2-mcspi: Configure hardware when slave driver changes mode · 97ca0d6c
      Mark A. Greer 提交于
      Commit id 2bd16e3e
      (spi: omap2-mcspi: Do not configure the controller
      on each transfer unless needed) does its job too
      well so omap2_mcspi_setup_transfer() isn't called
      even when an SPI slave driver changes 'spi->mode'.
      The result is that the mode requested by the SPI
      slave driver never takes effect.
      
      Fix this by adding the 'mode' member to the
      omap2_mcspi_cs structure which holds the mode
      value that the hardware is configured for.
      When the SPI slave driver changes 'spi->mode'
      it will be different than the value of this new
      member and the SPI master driver will know that
      the hardware must be reconfigured (by calling
      omap2_mcspi_setup_transfer()).
      
      Fixes: 2bd16e3e (spi: omap2-mcspi: Do not configure the controller on each transfer unless needed)
      Signed-off-by: NMark A. Greer <mgreer@animalcreek.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      Cc: stable@vger.kernel.org
      97ca0d6c
  12. 03 4月, 2014 1 次提交
  13. 19 2月, 2014 2 次提交
  14. 04 2月, 2014 2 次提交
  15. 03 2月, 2014 1 次提交
  16. 24 11月, 2013 1 次提交
  17. 17 10月, 2013 1 次提交
  18. 10 10月, 2013 1 次提交
  19. 26 9月, 2013 1 次提交
  20. 29 8月, 2013 1 次提交
  21. 30 7月, 2013 1 次提交
  22. 24 6月, 2013 1 次提交
  23. 18 6月, 2013 1 次提交
    • I
      spi: omap2-mcspi: Add FIFO buffer support · d33f473d
      Illia Smyrnov 提交于
      The MCSPI controller has a built-in FIFO buffer to unload the DMA or interrupt
      handler and improve data throughput. This patch adds FIFO buffer support for SPI
      transfers in DMA mode.
      
      For SPI transfers in DMA mode, the largest possible FIFO buffer size will be
      calculated and set up. The FIFO won't be used for the SPI transfers in DMA mode
      if: calculated FIFO buffer size is less then 2 bytes or the FIFO buffer size
      isn't multiple of the SPI word length.
      Signed-off-by: NIllia Smyrnov <illia.smyrnov@ti.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      d33f473d
  24. 17 6月, 2013 1 次提交
  25. 30 5月, 2013 1 次提交
  26. 23 5月, 2013 1 次提交
  27. 13 5月, 2013 1 次提交
  28. 18 4月, 2013 1 次提交
  29. 16 4月, 2013 1 次提交
  30. 01 4月, 2013 1 次提交
  31. 05 2月, 2013 1 次提交
  32. 26 1月, 2013 3 次提交
  33. 08 12月, 2012 1 次提交