[mirror_ubuntu-artful-kernel.git] / drivers / mmc / core / Kconfig

#
# MMC core configuration
#
config PWRSEQ_EMMC
	tristate "HW reset support for eMMC"
	default y
	depends on OF
	help
	  This selects Hardware reset support aka pwrseq-emmc for eMMC
	  devices. By default this option is set to y.

	  This driver can also be built as a module. If so, the module
	  will be called pwrseq_emmc.

config PWRSEQ_SD8787
	tristate "HW reset support for SD8787 BT + Wifi module"
	depends on OF && (MWIFIEX || BT_MRVL_SDIO)
	help
	  This selects hardware reset support for the SD8787 BT + Wifi
	  module. By default this option is set to n.

	  This driver can also be built as a module. If so, the module
	  will be called pwrseq_sd8787.

config PWRSEQ_SIMPLE
	tristate "Simple HW reset support for MMC"
	default y
	depends on OF
	help
	  This selects simple hardware reset support aka pwrseq-simple for MMC
	  devices. By default this option is set to y.

	  This driver can also be built as a module. If so, the module
	  will be called pwrseq_simple.

config MMC_BLOCK
	tristate "MMC block device driver"
	depends on BLOCK
	default y
	help
	  Say Y here to enable the MMC block device driver support.
	  This provides a block device driver, which you can use to
	  mount the filesystem. Almost everyone wishing MMC support
	  should say Y or M here.

config MMC_BLOCK_MINORS
	int "Number of minors per block device"
	depends on MMC_BLOCK
	range 4 256
	default 8
	help
	  Number of minors per block device. One is needed for every
	  partition on the disk (plus one for the whole disk).

	  Number of total MMC minors available is 256, so your number
	  of supported block devices will be limited to 256 divided
	  by this number.

	  Default is 8 to be backwards compatible with previous
	  hardwired device numbering.

	  If unsure, say 8 here.

config MMC_BLOCK_BOUNCE
	bool "Use bounce buffer for simple hosts"
	depends on MMC_BLOCK
	default y
	help
	  SD/MMC is a high latency protocol where it is crucial to
	  send large requests in order to get high performance. Many
	  controllers, however, are restricted to continuous memory
	  (i.e. they can't do scatter-gather), something the kernel
	  rarely can provide.

	  Say Y here to help these restricted hosts by bouncing
	  requests back and forth from a large buffer. You will get
	  a big performance gain at the cost of up to 64 KiB of
	  physical memory.

	  If unsure, say Y here.

config SDIO_UART
	tristate "SDIO UART/GPS class support"
	depends on TTY
	help
	  SDIO function driver for SDIO cards that implements the UART
	  class, as well as the GPS class which appears like a UART.

config MMC_TEST
	tristate "MMC host test driver"
	help
	  Development driver that performs a series of reads and writes
	  to a memory card in order to expose certain well known bugs
	  in host controllers. The tests are executed by writing to the
	  "test" file in debugfs under each card. Note that whatever is
	  on your card will be overwritten by these tests.

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