drivers/mmc/card/Kconfig

   1 #
   2 # MMC/SD card drivers
   3 #
   4
   5 comment "MMC/SD/SDIO Card Drivers"
   6
   7 config MMC_BLOCK
   8         tristate "MMC block device driver"
   9         depends on BLOCK
  10         default y
  11         help
  12           Say Y here to enable the MMC block device driver support.
  13           This provides a block device driver, which you can use to
  14           mount the filesystem. Almost everyone wishing MMC support
  15           should say Y or M here.
  16
  17 config MMC_BLOCK_BOUNCE
  18         bool "Use bounce buffer for simple hosts"
  19         depends on MMC_BLOCK
  20         default y
  21         help
  22           SD/MMC is a high latency protocol where it is crucial to
  23           send large requests in order to get high performance. Many
  24           controllers, however, are restricted to continuous memory
  25           (i.e. they can't do scatter-gather), something the kernel
  26           rarely can provide.
  27
  28           Say Y here to help these restricted hosts by bouncing
  29           requests back and forth from a large buffer. You will get
  30           a big performance gain at the cost of up to 64 KiB of
  31           physical memory.
  32
  33           If unsure, say Y here.
  34
  35 config SDIO_UART
  36         tristate "SDIO UART/GPS class support"
  37         help
  38           SDIO function driver for SDIO cards that implements the UART
  39           class, as well as the GPS class which appears like a UART.
  40
  41 config MMC_TEST
  42         tristate "MMC host test driver"
  43         default n
  44         help
  45           Development driver that performs a series of reads and writes
  46           to a memory card in order to expose certain well known bugs
  47           in host controllers. The tests are executed by writing to the
  48           "test" file in sysfs under each card. Note that whatever is
  49           on your card will be overwritten by these tests.
  50
  51           This driver is only of interest to those developing or
  52           testing a host driver. Most people should say N here.