Kconfig 2.7 KB

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