Kconfig 2.1 KB

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