1. 22 10月, 2013 1 次提交
  2. 27 9月, 2013 1 次提交
  3. 26 9月, 2013 5 次提交
  4. 25 8月, 2013 1 次提交
  5. 27 6月, 2013 2 次提交
  6. 31 5月, 2013 1 次提交
  7. 27 5月, 2013 2 次提交
    • L
      mmc: sdhci-esdhc-imx: fix multiblock reads on i.MX53 · 361b8482
      Lucas Stach 提交于
      The eSDHC controller on the i.MX53 needs an additional, non spec
      compliant CMD12 after a multiblock read with a predefined number of
      blocks. Otherwise the internal state machine won't go back to the
      idle state.
      
      This commit effectively reverts 5b6b0ad6 (mmc: sdhci-esdhc-imx:
      fix for mmc cards on i.MX5), which fixed part of the problem by
      making multiblock reads work, however this fix was not sufficient
      when multi- and singleblock reads got intermixed.
      
      This implements the recommended workaround (Freescale i.MX Reference
      Manual, section 29.6.8 "Multi-block Read") by manually sending a
      CMD12 with the RSPTYP bits cleared.
      Signed-off-by: NLucas Stach <l.stach@pengutronix.de>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      361b8482
    • M
      mmc: sdhci-esdhc-imx: Fix SDIO interrupts · f6825748
      Martin Fuzzey 提交于
      Currently SDIO interrupts do not work on i.MX53 and maybe others.
      
      This was observed with a Marvell 8787 based SDIO wifi adapter
      using the mwifiex driver and firmware from the Marvell git
      repository.
      The symptom was a timeout after firmware download.
      
      Observing the SDIO_DAT1 line showed that an interrupt was requested
      (level 0) but no interrupt was generated in software, the line
      stayed low until a timeout ocurred and the card was reset.
      
      There is a Freescale errata
      	ENGcm11186 "eSDHC misses SDIO interrupt when CINT is disabled"
      
      The workaround suggested by this errata is already implemented and
      involves clearing and then setting the D3CD bit in the host control
      register [see esdhc_writel_le()]
      
      However, when esdhc_writeb_le() is later used to write to
      SDHCI_HOST_CONTROL it always resets the D3CD bit.
      
      To fix this simply add the D3CD bit to the set of bits
      not modified by esdhc_writeb_le().
      Signed-off-by: NMartin Fuzzey <mfuzzey@parkeon.com>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      f6825748
  8. 23 3月, 2013 2 次提交
  9. 25 2月, 2013 9 次提交
  10. 12 2月, 2013 2 次提交
  11. 28 1月, 2013 2 次提交
  12. 07 12月, 2012 1 次提交
  13. 29 11月, 2012 3 次提交
  14. 14 9月, 2012 1 次提交
  15. 02 9月, 2012 1 次提交
  16. 23 7月, 2012 1 次提交
  17. 15 5月, 2012 1 次提交
  18. 11 5月, 2012 1 次提交
  19. 25 4月, 2012 1 次提交
    • S
      mmc sdhc i.MX: do not depend on grouped clocks · 52dac615
      Sascha Hauer 提交于
      the current i.MX clock support groups together unrelated clocks
      to a single clock which is then used by the driver. This can't
      be accomplished with the generic clock framework so we instead
      request the individual clocks in the driver. For i.MX there are
      generally three different clocks:
      
      ipg: bus clock (needed to access registers)
      ahb: dma relevant clock, sometimes referred to as hclk in the datasheet
      per: bit clock, pixel clock
      
      This patch changes the driver to request the individual clocks.
      Currently all clk_get will get the same clock until the SoCs
      are converted to the generic clock framework
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      52dac615
  20. 21 4月, 2012 1 次提交
  21. 05 3月, 2012 1 次提交
    • S
      mmc: sdhci-esdhc-imx: fix for mmc cards on i.MX5 · 5b6b0ad6
      Sascha Hauer 提交于
      On i.MX53 we have to write a special SDHCI_CMD_ABORTCMD to the
      SDHCI_TRANSFER_MODE register during a MMC_STOP_TRANSMISSION
      command. This works for SD cards. However, with MMC cards
      the MMC_SET_BLOCK_COUNT command is used instead, but this
      needs the same handling. Fix MMC cards by testing for the
      MMC_SET_BLOCK_COUNT command aswell. Tested on a custom i.MX53
      board with a Transcend MMC+ card and eMMC.
      
      The kernel started used MMC_SET_BLOCK_COUNT in 3.0, so this
      is a regression for these boards introduced in 3.0; it should
      go to 3.0/3.1/3.2-stable.
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      Acked-by: NShawn Guo <shawn.guo@linaro.org>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      5b6b0ad6