Kconfig 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158
  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_SD8787
  14. tristate "HW reset support for SD8787 BT + Wifi module"
  15. depends on OF && (MWIFIEX || BT_MRVL_SDIO)
  16. help
  17. This selects hardware reset support for the SD8787 BT + Wifi
  18. module. By default this option is set to n.
  19. This driver can also be built as a module. If so, the module
  20. will be called pwrseq_sd8787.
  21. config PWRSEQ_SIMPLE
  22. tristate "Simple HW reset support for MMC"
  23. default y
  24. depends on OF
  25. help
  26. This selects simple hardware reset support aka pwrseq-simple for MMC
  27. devices. By default this option is set to y.
  28. This driver can also be built as a module. If so, the module
  29. will be called pwrseq_simple.
  30. config MMC_BLOCK
  31. tristate "MMC block device driver"
  32. depends on BLOCK
  33. default y
  34. help
  35. Say Y here to enable the MMC block device driver support.
  36. This provides a block device driver, which you can use to
  37. mount the filesystem. Almost everyone wishing MMC support
  38. should say Y or M here.
  39. config MMC_BLOCK_MINORS
  40. int "Number of minors per block device"
  41. depends on MMC_BLOCK
  42. range 4 256
  43. default 8
  44. help
  45. Number of minors per block device. One is needed for every
  46. partition on the disk (plus one for the whole disk).
  47. Number of total MMC minors available is 256, so your number
  48. of supported block devices will be limited to 256 divided
  49. by this number.
  50. Default is 8 to be backwards compatible with previous
  51. hardwired device numbering.
  52. If unsure, say 8 here.
  53. config SDIO_UART
  54. tristate "SDIO UART/GPS class support"
  55. depends on TTY
  56. help
  57. SDIO function driver for SDIO cards that implements the UART
  58. class, as well as the GPS class which appears like a UART.
  59. config MMC_TEST
  60. tristate "MMC host test driver"
  61. help
  62. Development driver that performs a series of reads and writes
  63. to a memory card in order to expose certain well known bugs
  64. in host controllers. The tests are executed by writing to the
  65. "test" file in debugfs under each card. Note that whatever is
  66. on your card will be overwritten by these tests.
  67. This driver is only of interest to those developing or
  68. testing a host driver. Most people should say N here.
  69. config MMC_CRYPTO
  70. bool "MMC Crypto Engine Support"
  71. depends on BLK_INLINE_ENCRYPTION
  72. help
  73. Enable Crypto Engine Support in MMC.
  74. Enabling this makes it possible for the kernel to use the crypto
  75. capabilities of the MMC device (if present) to perform crypto
  76. operations on data being transferred to/from the device.
  77. config MMC_CRYPTO_LEGACY
  78. bool "MMC Crypto legacy Support"
  79. depends on BLK_INLINE_ENCRYPTION
  80. help
  81. Only for MTK legacy eMMC Crypto Engine, such as OTA projects
  82. of Android.
  83. Enabling this makes crypto data unit size is 512 bytes which
  84. used in MTK legacy eMMC Crypto Engine platforms.
  85. config MMC_BLOCK_IO_LOG
  86. bool "Block IO log"
  87. depends on MMC_BLOCK
  88. depends on MTK_BLOCK_TAG
  89. default y
  90. help
  91. The BLOCK TAG trace provides I/O logs for performance analysis and
  92. application access pattern study. The BLOCK TAG trace summarizes the
  93. I/O of each process every 1 second, and saves to ring buffer. The log
  94. can be displayed by "cat /sys/kernel/debug/blockio".
  95. The trace is default enabled on user and eng builts, say N here to
  96. disable it.
  97. config MMC_FFU
  98. bool "Field firmware updates to eMMC FW"
  99. depends on MMC
  100. help
  101. This is an option to run firmware update on eMMC 5.0.
  102. Field firmware updates (FFU) enables features enhancement
  103. in the field.
  104. This is must to upgrade the eMMC FW.
  105. config MMC_EMBEDDED_SDIO
  106. boolean "MMC embedded SDIO device support"
  107. help
  108. If you say Y here, support will be added for embedded SDIO
  109. devices which do not contain the necessary enumeration
  110. support in hardware to be properly detected.
  111. config MMC_PARANOID_SD_INIT
  112. bool "Enable paranoid SD card initialization"
  113. help
  114. If you say Y here, the MMC layer will be extra paranoid
  115. about re-trying SD init requests. This can be a useful
  116. work-around for buggy controllers and hardware. Enable
  117. if you are experiencing issues with SD detection.
  118. config MTK_MMC_PWR_WP
  119. bool "Kernel power-on write protect Support"
  120. depends on MMC
  121. help
  122. This is an option to set power-on write protect on the partitions which
  123. have already been defined in kernel. Currently, only for HUIWEI projects
  124. use.
  125. E.g. Kernel hard-code a partition named "system", User space use
  126. ioctl(fd, MMC_IOC_WP_CMD , &buf ) will set power-on write protect on it.
  127. config MMC_CRYPTO
  128. bool "MMC Crypto Engine Support"
  129. depends on BLK_INLINE_ENCRYPTION
  130. help
  131. Enable Crypto Engine Support in MMC.
  132. Enabling this makes it possible for the kernel to use the crypto
  133. capabilities of the MMC device (if present) to perform crypto
  134. operations on data being transferred to/from the device.