| Pierre Ossman | 1c6a071 | 2007-02-11 19:57:36 +0100 | [diff] [blame] | 1 | # |
| 2 | # MMC/SD card drivers |
| 3 | # |
| 4 | |
| 5 | comment "MMC/SD Card Drivers" |
| Pierre Ossman | 1c6a071 | 2007-02-11 19:57:36 +0100 | [diff] [blame] | 6 | |
| 7 | config MMC_BLOCK |
| 8 | tristate "MMC block device driver" |
| Jan Engelhardt | 790864d | 2007-05-08 22:30:32 +0200 | [diff] [blame] | 9 | depends on BLOCK |
| Pierre Ossman | 1c6a071 | 2007-02-11 19:57:36 +0100 | [diff] [blame] | 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 | |
| Pierre Ossman | 98ccf14 | 2007-05-12 00:26:16 +0200 | [diff] [blame] | 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 | |
| Nicolas Pitre | 6e418a9 | 2007-06-30 02:04:21 -0400 | [diff] [blame] | 35 | config SDIO_UART |
| 36 | tristate "SDIO UART/GPS class support" |
| 37 | depends on MMC |
| 38 | help |
| 39 | SDIO function driver for SDIO cards that implements the UART |
| 40 | class, as well as the GPS class which appears like a UART. |
| 41 | |
| Pierre Ossman | 88ae600 | 2007-08-12 14:23:50 +0200 | [diff] [blame] | 42 | config MMC_TEST |
| 43 | tristate "MMC host test driver" |
| 44 | default n |
| 45 | help |
| 46 | Development driver that performs a series of reads and writes |
| 47 | to a memory card in order to expose certain well known bugs |
| 48 | in host controllers. The tests are executed by writing to the |
| 49 | "test" file in sysfs under each card. Note that whatever is |
| 50 | on your card will be overwritten by these tests. |
| 51 | |
| 52 | This driver is only of interest to those developing or |
| 53 | testing a host driver. Most people should say N here. |