1. 01 5月, 2007 7 次提交
  2. 06 3月, 2007 1 次提交
  3. 05 2月, 2007 5 次提交
    • P
      mmc: Allow host drivers to specify max block count · 55db890a
      Pierre Ossman 提交于
      Many controllers have an upper limit on the number of blocks that can be
      transferred in one request. Allow the host drivers to specify this and make
      sure we avoid hitting this limit.
      
      Also change the max_sectors field to avoid confusion. This makes it map
      less directly to the block layer limits, but as they didn't apply directly
      on MMC cards anyway, this isn't a great loss.
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      55db890a
    • P
      mmc: Allow host drivers to specify a max block size · fe4a3c7a
      Pierre Ossman 提交于
      Most controllers have an upper limit on the block size. Allow the host
      drivers to specify this and make sure we avoid hitting this limit.
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      fe4a3c7a
    • P
      mmc: Add support for SDHC cards · fba68bd2
      Philip Langdale 提交于
      Thanks to the generous donation of an SDHC card by John Gilmore, and
      the surprisingly enlightened decision by the SD Card Association to
      publish useful specs, I've been able to bash out support for SDHC. The
      changes are not too profound:
      
      i) Add a card flag indicating the card uses block level addressing and
      check it in the block driver. As we never took advantage of byte-level
      addressing, this simply involves skipping the block -> byte
      translation when sending commands.
      
      ii) The layout of the CSD is changed - a set of fields are discarded
      to make space for a larger C_SIZE. We did not reference any of the
      discarded fields except those related to the C_SIZE.
      
      iii) Read and write timeouts are fixed values and not calculated from
      CSD values.
      
      iv) Before invoking SEND_APP_OP_COND, we must invoke the new
      SEND_IF_COND to inform the card we support SDHC.
      Signed-off-by: NPhilipl Langdale <philipl@overt.org>
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      fba68bd2
    • P
      mmc: let host be parent of cards · 11354d03
      Pierre Ossman 提交于
      Change the parent of cards to be a specific host (a class
      device), not the physical controller. This is particularly
      useful when the hardware has multiple slots, meaning
      multiple hosts.
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      11354d03
    • P
      mmc: replace host->card_busy · f22ee4ed
      Pierre Ossman 提交于
      As card_busy was only used to indicate if the host was exclusively
      claimed and not really used to identify a particular card, replacing
      it with just a boolean makes things a lot more easily understandable.
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      f22ee4ed
  4. 15 1月, 2007 1 次提交
  5. 02 12月, 2006 4 次提交
    • G
      Driver core: convert mmc code to use struct device · fcaf71fd
      Greg Kroah-Hartman 提交于
      Converts from using struct "class_device" to "struct device" making
      everything show up properly in /sys/devices/ with symlinks from the
      /sys/class directory.
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      fcaf71fd
    • P
      mmc: Support for high speed SD cards · 7ccd266e
      Pierre Ossman 提交于
      Modern SD cards support a clock speed of 50 MHz. Make sure we test for
      this capability and do the song and dance required to activate it.
      
      Activating high speed support actually modifies the TRAN_SPEED field
      of the CSD. But as the spec says that the cards must report 50 MHz,
      we might as well skip re-reading the CSD.
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      7ccd266e
    • P
      mmc: Add support for mmc v4 wide-bus modes · e45a1bd2
      Philip Langdale 提交于
      This change adds support for the mmc4 4-bit wide-bus mode.
      
      The mmc4 spec defines 8-bit and 4-bit transfer modes. As we do not support
      any 8-bit hardware, this patch only adds support for the 4-bit mode, but
      it can easily be built upon when the time comes.
      
      The 4-bit mode is electrically compatible with SD's 4-bit mode but the
      procedure for turning it on is different. This patch implements only
      the essential parts of the procedure as defined by the spec. Two additional
      steps are recommended but not compulsory. I am documenting them here so
      that there's a record.
      
      1) A bus-test mechanism is implemented using dedicated mmc commands which allow
      for testing the functionality of the data bus at the electrical level. This is
      pretty paranoid and they way the commands work is not compatible with the mmc
      subsystem (they don't set valid CRC values).
      
      2) MMC v4 cards can indicate they would like to draw more than the default
      amount of current in wide-bus modes. We currently will never switch the card
      into a higher draw mode. Supposedly, allowing the card to draw more current
      will let it perform better, but the specs seem to indicate that the card will
      function correctly without the mode change. Empirical testing supports this
      interpretation.
      Signed-off-by: NPhilip Langdale <philipl@overt.org>
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      e45a1bd2
    • P
      [PATCH] mmc: Add support for mmc v4 high speed mode · bce40a36
      Philip Langdale 提交于
      This adds support for the high-speed modes defined by mmc v4
      (assuming the host controller is up to it). On a TI sdhci controller,
      it improves read speed from 1.3MBps to 2.3MBps. The TI controller can
      only go up to 24MHz, but everything helps. Another person has taken
      this basic patch and used it on a Nokia 770 to get a bigger boost
      because that controller can run at 48MHZ.
      Signed-off-by: NPhilip Langdale <philipl@overt.org>
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      bce40a36
  6. 22 11月, 2006 1 次提交
  7. 06 10月, 2006 1 次提交
  8. 24 9月, 2006 1 次提交
    • R
      [MMC] MMC_CAP_BYTEBLOCK flag for non-log2 block sizes capable hosts · 42431acb
      Russell King 提交于
      Some MMC hosts can only handle log2 block sizes.  Unfortunately,
      the MMC password support needs to be able to send non-log2 block
      sizes.  Provide a capability so that the MMC password support can
      decide whether it should use this support or not.
      
      The unfortunate side effect of this host limitation is that any
      MMC card protected by a password which is not a log2 block size
      can not be accessed on a host which only allows a log2 block size.
      
      This change just adds the flag.  The MMC password support code
      needs updating to use it (if and when it is finally submitted.)
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      42431acb
  9. 16 9月, 2006 2 次提交
  10. 07 9月, 2006 2 次提交
  11. 20 5月, 2006 1 次提交
  12. 03 5月, 2006 1 次提交
  13. 22 2月, 2006 1 次提交
  14. 02 2月, 2006 1 次提交
  15. 10 1月, 2006 2 次提交
  16. 04 1月, 2006 2 次提交
  17. 29 11月, 2005 1 次提交
  18. 28 10月, 2005 1 次提交
  19. 09 9月, 2005 2 次提交
  20. 08 9月, 2005 3 次提交