Kconfig 2.1 KB

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