1. 12 9月, 2009 1 次提交
  2. 02 9月, 2009 1 次提交
  3. 08 8月, 2009 1 次提交
  4. 31 7月, 2009 3 次提交
  5. 30 7月, 2009 1 次提交
    • A
      sdhci: get rid of "frequency too high" flood when using eSDHC · a9e58f25
      Anton Vorontsov 提交于
      Since commit 8dfd0374 ("MMC core: limit
      minimum initialization frequency to 400kHz") MMC core checks for minimum
      frequency, and that causes following messages flood when using eSDHC
      controllers:
      
        ...
        mmc0: Minimum clock frequency too high for identification mode
        mmc0: Minimum clock frequency too high for identification mode
        ...
      
      The warnings are legitimate, since if we'd use 133 MHz clocks for standard
      SDHCI controllers, we'd not able to scale frequency down to 400 kHz.
      
      But eSDHC controllers have a non-standard SD clock management, so we can
      divide clock by 256 * 16, not just 256.
      
      This patch introduces get_min_clock() callback for sdhci core and
      implements it for sdhci-of driver, and thus fixes the issue.
      Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com>
      Cc: Matt Fleming <matt@console-pimps.org>
      Cc: Ian Molton <ian@mnementh.co.uk>
      Cc: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
      Cc: Pierre Ossman <drzeus@drzeus.cx>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a9e58f25
  6. 21 7月, 2009 1 次提交
  7. 09 7月, 2009 2 次提交
  8. 03 7月, 2009 1 次提交
  9. 01 7月, 2009 1 次提交
    • D
      spi: add spi_master flag word · 70d6027f
      David Brownell 提交于
      Add a new spi_master.flags word listing constraints relevant to that
      controller.  Define the first constraint bit: a half duplex restriction.
      Include that constraint in the OMAP1 MicroWire controller driver.
      
      Have the mmc_spi host be the first customer of this flag.  Its coding
      relies heavily on full duplex transfers, so it must fail when the
      underlying controller driver won't perform them.
      
      (The spi_write_then_read routine could use it too: use the
      temporarily-withdrawn full-duplex speedup unless this flag is set, in
      which case the existing code applies.  Similarly, any spi_master
      implementing only SPI_3WIRE should set the flag.)
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Cc: Marek Szyprowski <m.szyprowski@samsung.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      70d6027f
  10. 22 6月, 2009 8 次提交
  11. 16 6月, 2009 1 次提交
  12. 14 6月, 2009 19 次提交