2007-02-11 21:57:36 +03:00
|
|
|
#
|
|
|
|
|
# MMC/SD host controller drivers
|
|
|
|
|
#
|
|
|
|
|
|
2008-09-07 15:16:58 +04:00
|
|
|
comment "MMC/SD/SDIO Host Controller Drivers"
|
2007-02-11 21:57:36 +03:00
|
|
|
|
|
|
|
|
config MMC_ARMMMCI
|
|
|
|
|
tristate "ARM AMBA Multimedia Card Interface support"
|
2007-05-09 00:30:32 +04:00
|
|
|
depends on ARM_AMBA
|
2007-02-11 21:57:36 +03:00
|
|
|
help
|
|
|
|
|
This selects the ARM(R) AMBA(R) PrimeCell Multimedia Card
|
|
|
|
|
Interface (PL180 and PL181) support. If you have an ARM(R)
|
|
|
|
|
platform with a Multimedia Card slot, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MMC_PXA
|
|
|
|
|
tristate "Intel PXA25x/26x/27x Multimedia Card Interface support"
|
2007-05-09 00:30:32 +04:00
|
|
|
depends on ARCH_PXA
|
2007-02-11 21:57:36 +03:00
|
|
|
help
|
|
|
|
|
This selects the Intel(R) PXA(R) Multimedia card Interface.
|
|
|
|
|
If you have a PXA(R) platform with a Multimedia Card slot,
|
|
|
|
|
say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MMC_SDHCI
|
2008-01-06 01:18:58 +03:00
|
|
|
tristate "Secure Digital Host Controller Interface support"
|
2008-03-18 19:35:49 +03:00
|
|
|
depends on HAS_DMA
|
2007-02-11 21:57:36 +03:00
|
|
|
help
|
2008-03-18 19:35:49 +03:00
|
|
|
This selects the generic Secure Digital Host Controller Interface.
|
2007-02-11 21:57:36 +03:00
|
|
|
It is used by manufacturers such as Texas Instruments(R), Ricoh(R)
|
|
|
|
|
and Toshiba(R). Most controllers found in laptops are of this type.
|
2008-03-18 19:35:49 +03:00
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here. You
|
|
|
|
|
also need to enable an appropriate bus interface.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-03-17 00:13:46 +03:00
|
|
|
config MMC_SDHCI_IO_ACCESSORS
|
|
|
|
|
bool
|
|
|
|
|
depends on MMC_SDHCI
|
|
|
|
|
help
|
|
|
|
|
This is silent Kconfig symbol that is selected by the drivers that
|
|
|
|
|
need to overwrite SDHCI IO memory accessors.
|
|
|
|
|
|
2009-12-18 02:27:20 +03:00
|
|
|
config MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
|
|
|
|
|
bool
|
|
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
|
|
|
|
help
|
|
|
|
|
This option is selected by drivers running on big endian hosts
|
|
|
|
|
and performing I/O to a SDHCI controller through a bus that
|
|
|
|
|
implements a hardware byte swapper using a 32-bit datum.
|
|
|
|
|
This endian mapping mode is called "data invariance" and
|
|
|
|
|
has the effect of scrambling the addresses and formats of data
|
|
|
|
|
accessed in sizes other than the datum size.
|
|
|
|
|
|
2009-12-18 02:27:20 +03:00
|
|
|
This is the case for the Freescale eSDHC and Nintendo Wii SDHCI.
|
2009-12-18 02:27:20 +03:00
|
|
|
|
2008-03-18 19:35:49 +03:00
|
|
|
config MMC_SDHCI_PCI
|
|
|
|
|
tristate "SDHCI support on PCI bus"
|
|
|
|
|
depends on MMC_SDHCI && PCI
|
|
|
|
|
help
|
|
|
|
|
This selects the PCI Secure Digital Host Controller Interface.
|
|
|
|
|
Most controllers found today are PCI devices.
|
|
|
|
|
|
2007-02-11 21:57:36 +03:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-09-15 23:54:08 +04:00
|
|
|
config MMC_RICOH_MMC
|
ricoh_mmc: port from driver to pci quirk
This patch solves nasty problem original driver has.
Original goal of the ricoh_mmc was to disable this device because then,
mmc cards can be read using standard SDHCI controller, thus avoiding
writing of yet another driver.
However, the act of disablement, makes other pci functions that belong to
this controller (xD and memstick) shift up one level, thus pci core has
now wrong idea about these devices.
To fix this issue, this patch moves the driver into the pci quirk section,
thus it is executes before the pci is enumerated, and therefore solving
that issue, also same sequence of commands is performed on resume for same
reasons.
Also regardless of the above, this way is cleaner. You still need to set
CONFIG_MMC_RICOH_MMC to enable this quirk
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Acked-by: Philip Langdale <philipl@overt.org>
Acked-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-03-06 00:43:20 +03:00
|
|
|
bool "Ricoh MMC Controller Disabler (EXPERIMENTAL)"
|
2008-03-18 19:35:49 +03:00
|
|
|
depends on MMC_SDHCI_PCI
|
2007-09-15 23:54:08 +04:00
|
|
|
help
|
ricoh_mmc: port from driver to pci quirk
This patch solves nasty problem original driver has.
Original goal of the ricoh_mmc was to disable this device because then,
mmc cards can be read using standard SDHCI controller, thus avoiding
writing of yet another driver.
However, the act of disablement, makes other pci functions that belong to
this controller (xD and memstick) shift up one level, thus pci core has
now wrong idea about these devices.
To fix this issue, this patch moves the driver into the pci quirk section,
thus it is executes before the pci is enumerated, and therefore solving
that issue, also same sequence of commands is performed on resume for same
reasons.
Also regardless of the above, this way is cleaner. You still need to set
CONFIG_MMC_RICOH_MMC to enable this quirk
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Acked-by: Philip Langdale <philipl@overt.org>
Acked-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-03-06 00:43:20 +03:00
|
|
|
This adds a pci quirk to disable Ricoh MMC Controller. This
|
2007-09-15 23:54:08 +04:00
|
|
|
proprietary controller is unnecessary because the SDHCI driver
|
|
|
|
|
supports MMC cards on the SD controller, but if it is not
|
|
|
|
|
disabled, it will steal the MMC cards away - rendering them
|
ricoh_mmc: port from driver to pci quirk
This patch solves nasty problem original driver has.
Original goal of the ricoh_mmc was to disable this device because then,
mmc cards can be read using standard SDHCI controller, thus avoiding
writing of yet another driver.
However, the act of disablement, makes other pci functions that belong to
this controller (xD and memstick) shift up one level, thus pci core has
now wrong idea about these devices.
To fix this issue, this patch moves the driver into the pci quirk section,
thus it is executes before the pci is enumerated, and therefore solving
that issue, also same sequence of commands is performed on resume for same
reasons.
Also regardless of the above, this way is cleaner. You still need to set
CONFIG_MMC_RICOH_MMC to enable this quirk
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Acked-by: Philip Langdale <philipl@overt.org>
Acked-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: <linux-mmc@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2010-03-06 00:43:20 +03:00
|
|
|
useless. It is safe to select this even if you don't
|
2007-09-15 23:54:08 +04:00
|
|
|
have a Ricoh based card reader.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2009-03-17 00:14:05 +03:00
|
|
|
config MMC_SDHCI_OF
|
|
|
|
|
tristate "SDHCI support on OpenFirmware platforms"
|
|
|
|
|
depends on MMC_SDHCI && PPC_OF
|
|
|
|
|
help
|
|
|
|
|
This selects the OF support for Secure Digital Host Controller
|
2009-12-18 02:27:20 +03:00
|
|
|
Interfaces.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MMC_SDHCI_OF_ESDHC
|
|
|
|
|
bool "SDHCI OF support for the Freescale eSDHC controller"
|
|
|
|
|
depends on MMC_SDHCI_OF
|
|
|
|
|
select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
|
|
|
|
|
help
|
|
|
|
|
This selects the Freescale eSDHC controller support.
|
2009-03-17 00:14:05 +03:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-12-18 02:27:20 +03:00
|
|
|
config MMC_SDHCI_OF_HLWD
|
|
|
|
|
bool "SDHCI OF support for the Nintendo Wii SDHCI controllers"
|
|
|
|
|
depends on MMC_SDHCI_OF
|
|
|
|
|
select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
|
|
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
found in the "Hollywood" chipset of the Nintendo Wii video game
|
|
|
|
|
console.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-06-04 15:57:29 +04:00
|
|
|
config MMC_SDHCI_PLTFM
|
|
|
|
|
tristate "SDHCI support on the platform specific bus"
|
|
|
|
|
depends on MMC_SDHCI
|
|
|
|
|
help
|
|
|
|
|
This selects the platform specific bus support for Secure Digital Host
|
|
|
|
|
Controller Interface.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-06-14 16:52:37 +04:00
|
|
|
config MMC_SDHCI_S3C
|
|
|
|
|
tristate "SDHCI support on Samsung S3C SoC"
|
|
|
|
|
depends on MMC_SDHCI && (PLAT_S3C24XX || PLAT_S3C64XX)
|
|
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
often referrered to as the HSMMC block in some of the Samsung S3C
|
|
|
|
|
range of SoC.
|
|
|
|
|
|
|
|
|
|
Note, due to the problems with DMA, the DMA support is only
|
|
|
|
|
available with CONFIG_EXPERIMENTAL is selected.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-05-27 01:42:10 +04:00
|
|
|
config MMC_SDHCI_SPEAR
|
|
|
|
|
tristate "SDHCI support on ST SPEAr platform"
|
|
|
|
|
depends on MMC_SDHCI && PLAT_SPEAR
|
|
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
often referrered to as the HSMMC block in some of the ST SPEAR range
|
|
|
|
|
of SoC
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-06-14 16:52:37 +04:00
|
|
|
config MMC_SDHCI_S3C_DMA
|
|
|
|
|
bool "DMA support on S3C SDHCI"
|
|
|
|
|
depends on MMC_SDHCI_S3C && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Enable DMA support on the Samsung S3C SDHCI glue. The DMA
|
|
|
|
|
has proved to be problematic if the controller encounters
|
|
|
|
|
certain errors, and thus should be treated with care.
|
|
|
|
|
|
|
|
|
|
YMMV.
|
|
|
|
|
|
2007-02-11 21:57:36 +03:00
|
|
|
config MMC_OMAP
|
|
|
|
|
tristate "TI OMAP Multimedia Card Interface support"
|
2007-05-09 00:30:32 +04:00
|
|
|
depends on ARCH_OMAP
|
2007-02-11 21:57:36 +03:00
|
|
|
select TPS65010 if MACH_OMAP_H2
|
|
|
|
|
help
|
|
|
|
|
This selects the TI OMAP Multimedia card Interface.
|
|
|
|
|
If you have an OMAP board with a Multimedia Card slot,
|
|
|
|
|
say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-01-23 03:05:23 +03:00
|
|
|
config MMC_OMAP_HS
|
|
|
|
|
tristate "TI OMAP High Speed Multimedia Card Interface support"
|
2009-09-23 03:45:25 +04:00
|
|
|
depends on ARCH_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
|
2009-01-23 03:05:23 +03:00
|
|
|
help
|
|
|
|
|
This selects the TI OMAP High Speed Multimedia card Interface.
|
2009-09-23 03:45:25 +04:00
|
|
|
If you have an OMAP2430 or OMAP3 board or OMAP4 board with a
|
|
|
|
|
Multimedia Card slot, say Y or M here.
|
2009-01-23 03:05:23 +03:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-02-11 21:57:36 +03:00
|
|
|
config MMC_WBSD
|
|
|
|
|
tristate "Winbond W83L51xD SD/MMC Card Interface support"
|
2007-05-09 00:30:32 +04:00
|
|
|
depends on ISA_DMA_API
|
2007-02-11 21:57:36 +03:00
|
|
|
help
|
|
|
|
|
This selects the Winbond(R) W83L51xD Secure digital and
|
|
|
|
|
Multimedia card Interface.
|
|
|
|
|
If you have a machine with a integrated W83L518D or W83L519D
|
|
|
|
|
SD/MMC card reader, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MMC_AU1X
|
|
|
|
|
tristate "Alchemy AU1XX0 MMC Card Interface support"
|
2007-05-09 00:30:32 +04:00
|
|
|
depends on SOC_AU1200
|
2007-02-11 21:57:36 +03:00
|
|
|
help
|
|
|
|
|
This selects the AMD Alchemy(R) Multimedia card interface.
|
|
|
|
|
If you have a Alchemy platform with a MMC slot, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-09-23 03:45:19 +04:00
|
|
|
choice
|
|
|
|
|
prompt "Atmel SD/MMC Driver"
|
2010-03-06 00:43:22 +03:00
|
|
|
depends on AVR32 || ARCH_AT91
|
2009-09-23 03:45:19 +04:00
|
|
|
default MMC_ATMELMCI if AVR32
|
|
|
|
|
help
|
|
|
|
|
Choose which driver to use for the Atmel MCI Silicon
|
|
|
|
|
|
2007-02-11 21:57:36 +03:00
|
|
|
config MMC_AT91
|
|
|
|
|
tristate "AT91 SD/MMC Card Interface support"
|
2007-05-09 00:30:32 +04:00
|
|
|
depends on ARCH_AT91
|
2007-02-11 21:57:36 +03:00
|
|
|
help
|
|
|
|
|
This selects the AT91 MCI controller.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
atmel-mci: Driver for Atmel on-chip MMC controllers
This is a driver for the MMC controller on the AP7000 chips from
Atmel. It should in theory work on AT91 systems too with some
tweaking, but since the DMA interface is quite different, it's not
entirely clear if it's worth merging this with the at91_mci driver.
This driver has been around for a while in BSPs and kernel sources
provided by Atmel, but this particular version uses the generic DMA
Engine framework (with the slave extensions) instead of an
avr32-only DMA controller framework.
This driver can also use PIO transfers when no DMA channels are
available, and for transfers where using DMA may be difficult or
impractical for some reason (e.g. the DMA setup overhead is usually
not worth it for very short transfers, and badly aligned buffers or
lengths are difficult to handle.)
Currently, the driver only support PIO transfers. DMA support has been
split out to a separate patch to hopefully make it easier to review.
The driver has been tested using mmc-block and ext3fs on several SD,
SDHC and MMC+ cards. Reads and writes work fine, with read transfer
rates up to 3.5 MiB/s on fast cards with debugging disabled.
The driver has also been tested using the mmc_test module on the same
cards. All tests except 7, 9, 15 and 17 succeed. The first two are
unsupported by all the cards I have, so I don't know if the driver
handles this correctly. The last two fail because the hardware flags a
Data CRC Error instead of a Data Timeout error. I'm not sure how to deal
with that.
Documentation for this controller can be found in many data sheets from
Atmel, including the AT32AP7000 data sheet which can be found here:
http://www.atmel.com/dyn/products/datasheets.asp?family_id=682
Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2008-06-30 20:35:03 +04:00
|
|
|
config MMC_ATMELMCI
|
|
|
|
|
tristate "Atmel Multimedia Card Interface support"
|
2009-09-23 03:45:19 +04:00
|
|
|
depends on AVR32 || ARCH_AT91
|
atmel-mci: Driver for Atmel on-chip MMC controllers
This is a driver for the MMC controller on the AP7000 chips from
Atmel. It should in theory work on AT91 systems too with some
tweaking, but since the DMA interface is quite different, it's not
entirely clear if it's worth merging this with the at91_mci driver.
This driver has been around for a while in BSPs and kernel sources
provided by Atmel, but this particular version uses the generic DMA
Engine framework (with the slave extensions) instead of an
avr32-only DMA controller framework.
This driver can also use PIO transfers when no DMA channels are
available, and for transfers where using DMA may be difficult or
impractical for some reason (e.g. the DMA setup overhead is usually
not worth it for very short transfers, and badly aligned buffers or
lengths are difficult to handle.)
Currently, the driver only support PIO transfers. DMA support has been
split out to a separate patch to hopefully make it easier to review.
The driver has been tested using mmc-block and ext3fs on several SD,
SDHC and MMC+ cards. Reads and writes work fine, with read transfer
rates up to 3.5 MiB/s on fast cards with debugging disabled.
The driver has also been tested using the mmc_test module on the same
cards. All tests except 7, 9, 15 and 17 succeed. The first two are
unsupported by all the cards I have, so I don't know if the driver
handles this correctly. The last two fail because the hardware flags a
Data CRC Error instead of a Data Timeout error. I'm not sure how to deal
with that.
Documentation for this controller can be found in many data sheets from
Atmel, including the AT32AP7000 data sheet which can be found here:
http://www.atmel.com/dyn/products/datasheets.asp?family_id=682
Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2008-06-30 20:35:03 +04:00
|
|
|
help
|
|
|
|
|
This selects the Atmel Multimedia Card Interface driver. If
|
2009-09-23 03:45:19 +04:00
|
|
|
you have an AT32 (AVR32) or AT91 platform with a Multimedia
|
|
|
|
|
Card slot, say Y or M here.
|
atmel-mci: Driver for Atmel on-chip MMC controllers
This is a driver for the MMC controller on the AP7000 chips from
Atmel. It should in theory work on AT91 systems too with some
tweaking, but since the DMA interface is quite different, it's not
entirely clear if it's worth merging this with the at91_mci driver.
This driver has been around for a while in BSPs and kernel sources
provided by Atmel, but this particular version uses the generic DMA
Engine framework (with the slave extensions) instead of an
avr32-only DMA controller framework.
This driver can also use PIO transfers when no DMA channels are
available, and for transfers where using DMA may be difficult or
impractical for some reason (e.g. the DMA setup overhead is usually
not worth it for very short transfers, and badly aligned buffers or
lengths are difficult to handle.)
Currently, the driver only support PIO transfers. DMA support has been
split out to a separate patch to hopefully make it easier to review.
The driver has been tested using mmc-block and ext3fs on several SD,
SDHC and MMC+ cards. Reads and writes work fine, with read transfer
rates up to 3.5 MiB/s on fast cards with debugging disabled.
The driver has also been tested using the mmc_test module on the same
cards. All tests except 7, 9, 15 and 17 succeed. The first two are
unsupported by all the cards I have, so I don't know if the driver
handles this correctly. The last two fail because the hardware flags a
Data CRC Error instead of a Data Timeout error. I'm not sure how to deal
with that.
Documentation for this controller can be found in many data sheets from
Atmel, including the AT32AP7000 data sheet which can be found here:
http://www.atmel.com/dyn/products/datasheets.asp?family_id=682
Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
2008-06-30 20:35:03 +04:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-09-23 03:45:19 +04:00
|
|
|
endchoice
|
|
|
|
|
|
2008-07-30 22:29:03 +04:00
|
|
|
config MMC_ATMELMCI_DMA
|
|
|
|
|
bool "Atmel MCI DMA support (EXPERIMENTAL)"
|
2009-09-23 03:45:19 +04:00
|
|
|
depends on MMC_ATMELMCI && AVR32 && DMA_ENGINE && EXPERIMENTAL
|
2008-07-30 22:29:03 +04:00
|
|
|
help
|
|
|
|
|
Say Y here to have the Atmel MCI driver use a DMA engine to
|
|
|
|
|
do data transfers and thus increase the throughput and
|
|
|
|
|
reduce the CPU utilization. Note that this is highly
|
|
|
|
|
experimental and may cause the driver to lock up.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-02-11 21:57:36 +03:00
|
|
|
config MMC_IMX
|
|
|
|
|
tristate "Motorola i.MX Multimedia Card Interface support"
|
2009-04-01 14:40:15 +04:00
|
|
|
depends on ARCH_MX1
|
2007-02-11 21:57:36 +03:00
|
|
|
help
|
|
|
|
|
This selects the Motorola i.MX Multimedia card Interface.
|
|
|
|
|
If you have a i.MX platform with a Multimedia Card slot,
|
2009-01-06 19:04:14 +03:00
|
|
|
say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-09-23 03:44:22 +04:00
|
|
|
config MMC_MSM7X00A
|
|
|
|
|
tristate "Qualcomm MSM 7X00A SDCC Controller Support"
|
|
|
|
|
depends on MMC && ARCH_MSM
|
|
|
|
|
help
|
|
|
|
|
This provides support for the SD/MMC cell found in the
|
|
|
|
|
MSM 7X00A controllers from Qualcomm.
|
|
|
|
|
|
2009-01-06 19:04:14 +03:00
|
|
|
config MMC_MXC
|
|
|
|
|
tristate "Freescale i.MX2/3 Multimedia Card Interface support"
|
|
|
|
|
depends on ARCH_MXC
|
|
|
|
|
help
|
|
|
|
|
This selects the Freescale i.MX2/3 Multimedia card Interface.
|
|
|
|
|
If you have a i.MX platform with a Multimedia Card slot,
|
2007-02-11 21:57:36 +03:00
|
|
|
say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MMC_TIFM_SD
|
|
|
|
|
tristate "TI Flash Media MMC/SD Interface support (EXPERIMENTAL)"
|
2007-05-09 00:30:32 +04:00
|
|
|
depends on EXPERIMENTAL && PCI
|
2007-02-11 21:57:36 +03:00
|
|
|
select TIFM_CORE
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want to be able to access MMC/SD cards with
|
|
|
|
|
the Texas Instruments(R) Flash Media card reader, found in many
|
|
|
|
|
laptops.
|
|
|
|
|
This option 'selects' (turns on, enables) 'TIFM_CORE', but you
|
|
|
|
|
probably also need appropriate card reader host adapter, such as
|
|
|
|
|
'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
|
|
|
|
|
(TIFM_7XX1)'.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called tifm_sd.
|
|
|
|
|
|
2009-02-14 11:07:26 +03:00
|
|
|
config MMC_MVSDIO
|
|
|
|
|
tristate "Marvell MMC/SD/SDIO host driver"
|
|
|
|
|
depends on PLAT_ORION
|
|
|
|
|
---help---
|
|
|
|
|
This selects the Marvell SDIO host driver.
|
|
|
|
|
SDIO may currently be found on the Kirkwood 88F6281 and 88F6192
|
|
|
|
|
SoC controllers.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called mvsdio.
|
|
|
|
|
|
2009-12-15 05:01:21 +03:00
|
|
|
config MMC_DAVINCI
|
|
|
|
|
tristate "TI DAVINCI Multimedia Card Interface support"
|
|
|
|
|
depends on ARCH_DAVINCI
|
|
|
|
|
help
|
|
|
|
|
This selects the TI DAVINCI Multimedia card Interface.
|
|
|
|
|
If you have an DAVINCI board with a Multimedia Card slot,
|
|
|
|
|
say Y or M here. If unsure, say N.
|
|
|
|
|
|
2007-08-08 20:12:54 +04:00
|
|
|
config MMC_SPI
|
2008-09-07 15:16:58 +04:00
|
|
|
tristate "MMC/SD/SDIO over SPI"
|
2008-09-07 15:07:57 +04:00
|
|
|
depends on SPI_MASTER && !HIGHMEM && HAS_DMA
|
2007-08-08 20:12:54 +04:00
|
|
|
select CRC7
|
|
|
|
|
select CRC_ITU_T
|
|
|
|
|
help
|
2009-01-26 13:12:25 +03:00
|
|
|
Some systems access MMC/SD/SDIO cards using a SPI controller
|
2008-09-07 15:16:58 +04:00
|
|
|
instead of using a "native" MMC/SD/SDIO controller. This has a
|
|
|
|
|
disadvantage of being relatively high overhead, but a compensating
|
|
|
|
|
advantage of working on many systems without dedicated MMC/SD/SDIO
|
|
|
|
|
controllers.
|
2007-08-08 20:12:54 +04:00
|
|
|
|
|
|
|
|
If unsure, or if your system has no SPI master driver, say N.
|
|
|
|
|
|
2008-07-01 01:40:24 +04:00
|
|
|
config MMC_S3C
|
|
|
|
|
tristate "Samsung S3C SD/MMC Card Interface support"
|
2008-09-07 15:07:57 +04:00
|
|
|
depends on ARCH_S3C2410
|
2008-07-01 01:40:24 +04:00
|
|
|
help
|
|
|
|
|
This selects a driver for the MCI interface found in
|
|
|
|
|
Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs.
|
|
|
|
|
If you have a board based on one of those and a MMC/SD
|
|
|
|
|
slot, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-10-02 02:44:20 +04:00
|
|
|
config MMC_S3C_HW_SDIO_IRQ
|
|
|
|
|
bool "Hardware support for SDIO IRQ"
|
|
|
|
|
depends on MMC_S3C
|
|
|
|
|
help
|
|
|
|
|
Enable the hardware support for SDIO interrupts instead of using
|
|
|
|
|
the generic polling code.
|
|
|
|
|
|
2009-10-02 02:44:18 +04:00
|
|
|
choice
|
|
|
|
|
prompt "Samsung S3C SD/MMC transfer code"
|
|
|
|
|
depends on MMC_S3C
|
|
|
|
|
|
|
|
|
|
config MMC_S3C_PIO
|
|
|
|
|
bool "Use PIO transfers only"
|
|
|
|
|
help
|
|
|
|
|
Use PIO to transfer data between memory and the hardware.
|
|
|
|
|
|
|
|
|
|
PIO is slower than DMA as it requires CPU instructions to
|
|
|
|
|
move the data. This has been the traditional default for
|
|
|
|
|
the S3C MCI driver.
|
|
|
|
|
|
|
|
|
|
config MMC_S3C_DMA
|
|
|
|
|
bool "Use DMA transfers only (EXPERIMENTAL)"
|
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
Use DMA to transfer data between memory and the hardare.
|
|
|
|
|
|
|
|
|
|
Currently, the DMA support in this driver seems to not be
|
|
|
|
|
working properly and needs to be debugged before this
|
|
|
|
|
option is useful.
|
|
|
|
|
|
|
|
|
|
config MMC_S3C_PIODMA
|
|
|
|
|
bool "Support for both PIO and DMA (EXPERIMENTAL)"
|
|
|
|
|
help
|
|
|
|
|
Compile both the PIO and DMA transfer routines into the
|
|
|
|
|
driver and let the platform select at run-time which one
|
|
|
|
|
is best.
|
|
|
|
|
|
|
|
|
|
See notes for the DMA option.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2008-07-15 16:21:29 +04:00
|
|
|
config MMC_SDRICOH_CS
|
|
|
|
|
tristate "MMC/SD driver for Ricoh Bay1Controllers (EXPERIMENTAL)"
|
2008-09-07 15:07:57 +04:00
|
|
|
depends on EXPERIMENTAL && PCI && PCMCIA
|
2008-07-15 16:21:29 +04:00
|
|
|
help
|
|
|
|
|
Say Y here if your Notebook reports a Ricoh Bay1Controller PCMCIA
|
|
|
|
|
card whenever you insert a MMC or SD card into the card slot.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called sdricoh_cs.
|
|
|
|
|
|
2008-07-15 19:02:21 +04:00
|
|
|
config MMC_TMIO
|
|
|
|
|
tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
|
2010-02-22 07:40:59 +03:00
|
|
|
depends on MFD_TMIO || MFD_ASIC3 || MFD_SH_MOBILE_SDHI
|
2008-07-15 19:02:21 +04:00
|
|
|
help
|
|
|
|
|
This provides support for the SD/MMC cell found in TC6393XB,
|
2009-06-04 22:12:37 +04:00
|
|
|
T7L66XB and also HTC ASIC3
|
2009-05-22 22:33:59 +04:00
|
|
|
|
|
|
|
|
config MMC_CB710
|
|
|
|
|
tristate "ENE CB710 MMC/SD Interface support"
|
|
|
|
|
depends on PCI
|
|
|
|
|
select CB710_CORE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for MMC/SD part of ENE CB710/720 Flash
|
|
|
|
|
memory card reader found in some laptops (ie. some versions of
|
|
|
|
|
HP Compaq nx9500).
|
|
|
|
|
|
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
|
|
|
will be called cb710-mmc.
|
|
|
|
|
|
2009-06-17 22:22:39 +04:00
|
|
|
config MMC_VIA_SDMMC
|
|
|
|
|
tristate "VIA SD/MMC Card Reader Driver"
|
|
|
|
|
depends on PCI
|
|
|
|
|
help
|
|
|
|
|
This selects the VIA SD/MMC Card Reader driver, say Y or M here.
|
|
|
|
|
VIA provides one multi-functional card reader which integrated into
|
|
|
|
|
some motherboards manufactured by VIA. This card reader supports
|
|
|
|
|
SD/MMC/SDHC.
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2009-12-15 05:01:32 +03:00
|
|
|
|
|
|
|
|
config SDH_BFIN
|
|
|
|
|
tristate "Blackfin Secure Digital Host support"
|
2010-03-06 00:43:24 +03:00
|
|
|
depends on (BF54x && !BF544) || (BF51x && !BF512)
|
2009-12-15 05:01:32 +03:00
|
|
|
help
|
|
|
|
|
If you say yes here you will get support for the Blackfin on-chip
|
|
|
|
|
Secure Digital Host interface. This includes support for MMC and
|
|
|
|
|
SD cards.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called bfin_sdh.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND
|
|
|
|
|
bool "Blackfin EZkit Missing SDH_CMD Pull Up Resistor Workaround"
|
|
|
|
|
depends on SDH_BFIN
|
|
|
|
|
help
|
|
|
|
|
If you say yes here SD-Cards may work on the EZkit.
|
2010-05-27 01:41:59 +04:00
|
|
|
|
|
|
|
|
config MMC_SH_MMCIF
|
|
|
|
|
tristate "SuperH Internal MMCIF support"
|
|
|
|
|
depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
|
|
|
|
|
help
|
|
|
|
|
This selects the MMC Host Interface controler (MMCIF).
|
|
|
|
|
|
|
|
|
|
This driver supports MMCIF in sh7724/sh7757/sh7372.
|
