2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2007-02-12 02:57:36 +08:00
|
|
|
#
|
|
|
|
|
# MMC/SD host controller drivers
|
|
|
|
|
#
|
|
|
|
|
|
2008-09-07 19:16:58 +08:00
|
|
|
comment "MMC/SD/SDIO Host Controller Drivers"
|
2007-02-12 02:57:36 +08:00
|
|
|
|
2017-07-19 15:55:47 +08:00
|
|
|
config MMC_DEBUG
|
2017-09-06 02:27:50 +08:00
|
|
|
bool "MMC host drivers debugging"
|
2017-07-19 15:55:47 +08:00
|
|
|
depends on MMC != n
|
|
|
|
|
help
|
|
|
|
|
This is an option for use by developers; most people should
|
|
|
|
|
say N here. This enables MMC host driver debugging. And further
|
|
|
|
|
added host drivers please don't invent their private macro for
|
|
|
|
|
debugging.
|
|
|
|
|
|
2007-02-12 02:57:36 +08:00
|
|
|
config MMC_ARMMMCI
|
|
|
|
|
tristate "ARM AMBA Multimedia Card Interface support"
|
2007-05-09 04:30:32 +08:00
|
|
|
depends on ARM_AMBA
|
2007-02-12 02:57:36 +08: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.
|
|
|
|
|
|
2014-07-29 10:50:30 +08:00
|
|
|
config MMC_QCOM_DML
|
2017-08-30 20:22:12 +08:00
|
|
|
bool "Qualcomm Data Mover for SD Card Controller"
|
2014-07-29 10:50:30 +08:00
|
|
|
depends on MMC_ARMMMCI && QCOM_BAM_DMA
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This selects the Qualcomm Data Mover lite/local on SD Card controller.
|
|
|
|
|
This option will enable the dma to work correctly, if you are using
|
|
|
|
|
Qcom SOCs and MMC, you would probably need this option to get DMA working.
|
|
|
|
|
|
|
|
|
|
if unsure, say N.
|
|
|
|
|
|
2018-10-08 20:08:55 +08:00
|
|
|
config MMC_STM32_SDMMC
|
|
|
|
|
bool "STMicroelectronics STM32 SDMMC Controller"
|
|
|
|
|
depends on MMC_ARMMMCI
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This selects the STMicroelectronics STM32 SDMMC host controller.
|
|
|
|
|
If you have a STM32 sdmmc host with internal DMA say Y here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-02-12 02:57:36 +08:00
|
|
|
config MMC_PXA
|
|
|
|
|
tristate "Intel PXA25x/26x/27x Multimedia Card Interface support"
|
2007-05-09 04:30:32 +08:00
|
|
|
depends on ARCH_PXA
|
2007-02-12 02:57:36 +08: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 06:18:58 +08:00
|
|
|
tristate "Secure Digital Host Controller Interface support"
|
2008-03-19 00:35:49 +08:00
|
|
|
depends on HAS_DMA
|
2007-02-12 02:57:36 +08:00
|
|
|
help
|
2008-03-19 00:35:49 +08:00
|
|
|
This selects the generic Secure Digital Host Controller Interface.
|
2007-02-12 02:57:36 +08: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-19 00:35:49 +08: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 05:13:46 +08: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 07:27:20 +08:00
|
|
|
config MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
|
|
|
|
|
bool
|
2015-01-26 18:35:44 +08:00
|
|
|
depends on MMC_SDHCI
|
2009-12-18 07:27:20 +08:00
|
|
|
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.
|
|
|
|
|
|
2015-10-08 18:36:47 +08:00
|
|
|
This is the case for the Nintendo Wii SDHCI.
|
2009-12-18 07:27:20 +08:00
|
|
|
|
2008-03-19 00:35:49 +08:00
|
|
|
config MMC_SDHCI_PCI
|
|
|
|
|
tristate "SDHCI support on PCI bus"
|
|
|
|
|
depends on MMC_SDHCI && PCI
|
2017-11-29 21:41:06 +08:00
|
|
|
select MMC_CQHCI
|
2019-05-06 16:38:53 +08:00
|
|
|
select IOSF_MBI if X86
|
2019-09-11 15:23:44 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2008-03-19 00:35:49 +08:00
|
|
|
help
|
|
|
|
|
This selects the PCI Secure Digital Host Controller Interface.
|
|
|
|
|
Most controllers found today are PCI devices.
|
|
|
|
|
|
2007-02-12 02:57:36 +08:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-09-16 03:54:08 +08:00
|
|
|
config MMC_RICOH_MMC
|
2012-10-03 02:17:47 +08:00
|
|
|
bool "Ricoh MMC Controller Disabler"
|
2008-03-19 00:35:49 +08:00
|
|
|
depends on MMC_SDHCI_PCI
|
2015-01-26 18:44:15 +08:00
|
|
|
default y
|
2007-09-16 03:54:08 +08: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 05:43:20 +08:00
|
|
|
This adds a pci quirk to disable Ricoh MMC Controller. This
|
2007-09-16 03:54:08 +08: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 05:43:20 +08:00
|
|
|
useless. It is safe to select this even if you don't
|
2007-09-16 03:54:08 +08:00
|
|
|
have a Ricoh based card reader.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2012-11-24 04:17:34 +08:00
|
|
|
config MMC_SDHCI_ACPI
|
|
|
|
|
tristate "SDHCI support for ACPI enumerated SDHCI controllers"
|
2019-01-05 18:06:04 +08:00
|
|
|
depends on MMC_SDHCI && ACPI && PCI
|
2016-04-15 19:06:57 +08:00
|
|
|
select IOSF_MBI if X86
|
2012-11-24 04:17:34 +08:00
|
|
|
help
|
|
|
|
|
This selects support for ACPI enumerated SDHCI controllers,
|
|
|
|
|
identified by ACPI Compatibility ID PNP0D40 or specific
|
|
|
|
|
ACPI Hardware IDs.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-06-02 10:57:50 +08:00
|
|
|
config MMC_SDHCI_PLTFM
|
|
|
|
|
tristate "SDHCI platform and OF driver helper"
|
2011-05-27 23:48:14 +08:00
|
|
|
depends on MMC_SDHCI
|
2011-06-02 10:57:50 +08:00
|
|
|
help
|
|
|
|
|
This selects the common helper functions support for Secure Digital
|
|
|
|
|
Host Controller Interface based platform and OF drivers.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2013-12-03 02:02:36 +08:00
|
|
|
config MMC_SDHCI_OF_ARASAN
|
|
|
|
|
tristate "SDHCI OF support for the Arasan SDHCI controllers"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
depends on OF
|
2016-06-21 01:56:50 +08:00
|
|
|
depends on COMMON_CLK
|
2018-01-16 11:43:51 +08:00
|
|
|
select MMC_CQHCI
|
2013-12-03 02:02:36 +08:00
|
|
|
help
|
|
|
|
|
This selects the Arasan Secure Digital Host Controller Interface
|
|
|
|
|
(SDHCI). This hardware is found e.g. in Xilinx' Zynq SoC.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2019-08-07 08:36:29 +08:00
|
|
|
config MMC_SDHCI_OF_ASPEED
|
|
|
|
|
tristate "SDHCI OF support for the ASPEED SDHCI controller"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
2019-09-04 10:21:20 +08:00
|
|
|
depends on OF && OF_ADDRESS
|
2019-11-18 18:46:45 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2019-08-07 08:36:29 +08:00
|
|
|
help
|
|
|
|
|
This selects the ASPEED Secure Digital Host Controller Interface.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2021-01-14 11:14:31 +08:00
|
|
|
config MMC_SDHCI_OF_ASPEED_TEST
|
|
|
|
|
bool "Tests for the ASPEED SDHCI driver"
|
|
|
|
|
depends on MMC_SDHCI_OF_ASPEED && KUNIT=y
|
|
|
|
|
help
|
|
|
|
|
Enable KUnit tests for the ASPEED SDHCI driver. Select this
|
|
|
|
|
option only if you will boot the kernel for the purpose of running
|
|
|
|
|
unit tests (e.g. under UML or qemu).
|
|
|
|
|
|
|
|
|
|
The KUnit tests generally exercise parts of the driver that do not
|
|
|
|
|
directly touch the hardware, for example, the phase correction
|
|
|
|
|
calculations.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-07-29 22:22:47 +08:00
|
|
|
config MMC_SDHCI_OF_AT91
|
|
|
|
|
tristate "SDHCI OF support for the Atmel SDMMC controller"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
2020-04-22 23:34:01 +08:00
|
|
|
depends on OF && HAVE_CLK
|
2015-07-29 22:22:47 +08:00
|
|
|
help
|
|
|
|
|
This selects the Atmel SDMMC driver
|
|
|
|
|
|
2011-06-02 10:57:50 +08:00
|
|
|
config MMC_SDHCI_OF_ESDHC
|
|
|
|
|
tristate "SDHCI OF support for the Freescale eSDHC controller"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on PPC || ARCH_MXC || ARCH_LAYERSCAPE || COMPILE_TEST
|
2015-10-08 18:36:47 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2016-11-09 11:14:12 +08:00
|
|
|
select FSL_GUTS
|
2009-12-18 07:27:20 +08:00
|
|
|
help
|
|
|
|
|
This selects the Freescale eSDHC controller support.
|
2009-03-17 05:14:05 +08:00
|
|
|
|
2011-06-02 10:57:50 +08:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
2009-03-17 05:14:05 +08:00
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-12-18 07:27:20 +08:00
|
|
|
config MMC_SDHCI_OF_HLWD
|
2011-06-02 10:57:50 +08:00
|
|
|
tristate "SDHCI OF support for the Nintendo Wii SDHCI controllers"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
2015-02-26 20:08:21 +08:00
|
|
|
depends on PPC
|
2009-12-18 07:27:20 +08:00
|
|
|
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.
|
|
|
|
|
|
2011-06-02 10:57:50 +08:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
2009-12-18 07:27:20 +08:00
|
|
|
If unsure, say N.
|
|
|
|
|
|
2018-07-06 15:23:55 +08:00
|
|
|
config MMC_SDHCI_OF_DWCMSHC
|
|
|
|
|
tristate "SDHCI OF support for the Synopsys DWC MSHC"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
depends on OF
|
|
|
|
|
depends on COMMON_CLK
|
|
|
|
|
help
|
|
|
|
|
This selects Synopsys DesignWare Cores Mobile Storage Controller
|
|
|
|
|
support.
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-08-25 16:13:56 +08:00
|
|
|
config MMC_SDHCI_OF_SPARX5
|
|
|
|
|
tristate "SDHCI OF support for the MCHP Sparx5 SoC"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_SPARX5 || COMPILE_TEST
|
2020-08-25 16:13:56 +08:00
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
found in the MCHP Sparx5 SoC.
|
|
|
|
|
|
|
|
|
|
If you have a Sparx5 SoC with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2016-12-08 20:50:55 +08:00
|
|
|
config MMC_SDHCI_CADENCE
|
|
|
|
|
tristate "SDHCI support for the Cadence SD/SDIO/eMMC controller"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This selects the Cadence SD/SDIO/eMMC driver.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-08-11 09:01:49 +08:00
|
|
|
config MMC_SDHCI_CNS3XXX
|
2011-05-27 23:48:12 +08:00
|
|
|
tristate "SDHCI support on the Cavium Networks CNS3xxx SoC"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_CNS3XXX || COMPILE_TEST
|
2011-06-02 10:57:50 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2010-08-11 09:01:49 +08:00
|
|
|
help
|
|
|
|
|
This selects the SDHCI support for CNS3xxx System-on-Chip devices.
|
|
|
|
|
|
2011-06-02 10:57:50 +08:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
2010-08-11 09:01:49 +08:00
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-05-19 03:17:41 +08:00
|
|
|
config MMC_SDHCI_ESDHC_MCF
|
|
|
|
|
tristate "SDHCI support for the Freescale eSDHC ColdFire controller"
|
|
|
|
|
depends on M5441x
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
|
|
|
|
help
|
|
|
|
|
This selects the Freescale eSDHC controller support for
|
|
|
|
|
ColdFire mcf5441x devices.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-10-15 18:21:04 +08:00
|
|
|
config MMC_SDHCI_ESDHC_IMX
|
2011-09-19 17:32:21 +08:00
|
|
|
tristate "SDHCI support for the Freescale eSDHC/uSDHC i.MX controller"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_MXC || COMPILE_TEST
|
2011-06-02 10:57:50 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2021-03-15 07:08:23 +08:00
|
|
|
depends on OF
|
2010-10-15 18:21:04 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2019-01-07 18:11:39 +08:00
|
|
|
select MMC_CQHCI
|
2010-10-15 18:21:04 +08:00
|
|
|
help
|
2011-09-19 17:32:21 +08:00
|
|
|
This selects the Freescale eSDHC/uSDHC controller support
|
|
|
|
|
found on i.MX25, i.MX35 i.MX5x and i.MX6x.
|
2010-10-15 18:21:04 +08:00
|
|
|
|
2011-06-02 10:57:50 +08:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
2010-10-15 18:21:04 +08:00
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-11-08 05:57:12 +08:00
|
|
|
config MMC_SDHCI_DOVE
|
2011-05-27 23:48:12 +08:00
|
|
|
tristate "SDHCI support on Marvell's Dove SoC"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_DOVE || MACH_DOVE || COMPILE_TEST
|
2011-06-02 10:57:50 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2010-11-08 05:57:12 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
|
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface in
|
|
|
|
|
Marvell's Dove SoC.
|
|
|
|
|
|
2011-06-02 10:57:50 +08:00
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
2010-11-08 05:57:12 +08:00
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-01-02 12:52:56 +08:00
|
|
|
config MMC_SDHCI_TEGRA
|
2011-05-27 23:48:12 +08:00
|
|
|
tristate "SDHCI platform support for the Tegra SD/MMC Controller"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_TEGRA || COMPILE_TEST
|
2011-06-02 10:57:50 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2011-01-02 12:52:56 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2019-01-24 03:30:54 +08:00
|
|
|
select MMC_CQHCI
|
2011-01-02 12:52:56 +08:00
|
|
|
help
|
|
|
|
|
This selects the Tegra SD/MMC controller. If you have a Tegra
|
|
|
|
|
platform with SD or MMC devices, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-06-14 20:52:37 +08:00
|
|
|
config MMC_SDHCI_S3C
|
|
|
|
|
tristate "SDHCI support on Samsung S3C SoC"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on MMC_SDHCI
|
ARM: SoC platform updates
SoC changes, a substantial part of this is cleanup of some of the older
platforms that used to have a bunch of board files. In particular:
- Removal of non-DT i.MX platforms that haven't seen activity in years,
it's time to remove them.
- A bunch of cleanup and removal of platform data for TI/OMAP platforms,
moving over to genpd for power/reset control (yay!)
- Major cleanup of Samsung S3C24xx and S3C64xx platforms, moving them
closer to multiplatform support (not quite there yet, but getting
close).
THere are a few other changes too, smaller fixlets, etc. For new
platform support, the primary ones re:
- New SoC: Hisilicon SD5203, ARM926EJ-S platform.
- Cpufreq support for i.MX7ULP
-----BEGIN PGP SIGNATURE-----
iQJDBAABCgAtFiEElf+HevZ4QCAJmMQ+jBrnPN6EHHcFAl+TT4gPHG9sb2ZAbGl4
b20ubmV0AAoJEIwa5zzehBx322MP/1mI56SyOFx30AqtWBPSjHJp+DzhOObyb4vD
ndYuicBIn9tJwvVRBBZkfsbIU8EENVwrN3hOpesaj9L7xiqOqKakcnyC1REYmpIs
8XBDfdZzy5PrMHIu3fF1ZDCQyO7KndGf5DfLVxJtcf1tSPQyQCuIA3FtS6d8Bxnz
r491+om67ucnlFD5X0Spm3RdZH+ECmXx2iXwoS0Zi7P+X+S+ovG8wBV/X0ggeoBc
Zgi4W01SiRupmSVZ6PA7FvWaLGQErQAALQOcFtMcFgjeWzc1v2QzcURELH8JW7ro
72AH9st1Kvi3hoN2HNNzUnNUdQvZ+AdH8skMIpN/e1cBYqYStAF3gm/R9h+iVHbG
GMmgzXHAFErfAW2UcF8tq1CzvQ5ChcTLNXdeoa8CeQbcDfocF3EyuKSPuDH+ve0H
kk4tPesTAc6XCEVwLaGnoC75sdum5mSi8h9vqhln2KCdeTY7jxzH9YGHjm71Supb
kV9vqo5Q5U/c5l2nU4r5q/DZdIahKsk3HIQZ0iG7BifAzamaTh4uyLVjtM6HSwNz
tdHZaxoHd/PLI5IoeggFelx6qgvK5qVRLP0evgOdTLRFLj/ZbrOf0Q7DjdTy2BjZ
Lgq461QqNapOzxq43G2IDT2+P62Q1+d+YLCKBgaGQaJicyU5m9STCNo3UBb1qH1h
W6UwGF5z
=0+Ee
-----END PGP SIGNATURE-----
Merge tag 'armsoc-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
Pull ARM SoC platform updates from Olof Johansson:
"SoC changes, a substantial part of this is cleanup of some of the
older platforms that used to have a bunch of board files.
In particular:
- Remove non-DT i.MX platforms that haven't seen activity in years,
it's time to remove them.
- A bunch of cleanup and removal of platform data for TI/OMAP
platforms, moving over to genpd for power/reset control (yay!)
- Major cleanup of Samsung S3C24xx and S3C64xx platforms, moving them
closer to multiplatform support (not quite there yet, but getting
close).
There are a few other changes too, smaller fixlets, etc. For new
platform support, the primary ones are:
- New SoC: Hisilicon SD5203, ARM926EJ-S platform.
- Cpufreq support for i.MX7ULP"
* tag 'armsoc-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc: (121 commits)
ARM: mstar: Select MStar intc
ARM: stm32: Replace HTTP links with HTTPS ones
ARM: debug: add UART early console support for SD5203
ARM: hisi: add support for SD5203 SoC
ARM: omap3: enable off mode automatically
clk: imx: imx35: Remove mx35_clocks_init()
clk: imx: imx31: Remove mx31_clocks_init()
clk: imx: imx27: Remove mx27_clocks_init()
ARM: imx: Remove unused definitions
ARM: imx35: Retrieve the IIM base address from devicetree
ARM: imx3: Retrieve the AVIC base address from devicetree
ARM: imx3: Retrieve the CCM base address from devicetree
ARM: imx31: Retrieve the IIM base address from devicetree
ARM: imx27: Retrieve the CCM base address from devicetree
ARM: imx27: Retrieve the SYSCTRL base address from devicetree
ARM: s3c64xx: bring back notes from removed debug-macro.S
ARM: s3c24xx: fix Wunused-variable warning on !MMU
ARM: samsung: fix PM debug build with DEBUG_LL but !MMU
MAINTAINERS: mark linux-samsung-soc list non-moderated
ARM: imx: Remove remnant board file support pieces
...
2020-10-25 01:33:08 +08:00
|
|
|
depends on PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST
|
2009-06-14 20:52:37 +08:00
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-06-08 17:41:57 +08:00
|
|
|
config MMC_SDHCI_PXAV3
|
|
|
|
|
tristate "Marvell MMP2 SD Host Controller support (PXAV3)"
|
2021-05-31 17:48:49 +08:00
|
|
|
depends on HAVE_CLK
|
2014-06-06 05:14:41 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2015-02-23 18:30:40 +08:00
|
|
|
depends on ARCH_BERLIN || ARCH_MMP || ARCH_MVEBU || COMPILE_TEST
|
2011-06-08 17:41:57 +08:00
|
|
|
default CPU_MMP2
|
|
|
|
|
help
|
|
|
|
|
This selects the Marvell(R) PXAV3 SD Host Controller.
|
|
|
|
|
If you have a MMP2 platform with SD Host Controller
|
|
|
|
|
and a card slot, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-06-08 17:41:58 +08:00
|
|
|
config MMC_SDHCI_PXAV2
|
|
|
|
|
tristate "Marvell PXA9XX SD Host Controller support (PXAV2)"
|
2021-05-31 17:48:49 +08:00
|
|
|
depends on HAVE_CLK
|
2014-06-06 05:14:41 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2015-01-26 18:23:28 +08:00
|
|
|
depends on ARCH_MMP || COMPILE_TEST
|
2011-06-08 17:41:58 +08:00
|
|
|
default CPU_PXA910
|
|
|
|
|
help
|
|
|
|
|
This selects the Marvell(R) PXAV2 SD Host Controller.
|
|
|
|
|
If you have a PXA9XX platform with SD Host Controller
|
|
|
|
|
and a card slot, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-05-27 05:42:10 +08:00
|
|
|
config MMC_SDHCI_SPEAR
|
|
|
|
|
tristate "SDHCI support on ST SPEAr platform"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on MMC_SDHCI
|
|
|
|
|
depends on PLAT_SPEAR || COMPILE_TEST
|
2015-03-04 21:57:44 +08:00
|
|
|
depends on OF
|
2010-05-27 05:42:10 +08:00
|
|
|
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 20:52:37 +08:00
|
|
|
config MMC_SDHCI_S3C_DMA
|
|
|
|
|
bool "DMA support on S3C SDHCI"
|
2012-10-03 02:17:47 +08:00
|
|
|
depends on MMC_SDHCI_S3C
|
2009-06-14 20:52:37 +08:00
|
|
|
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.
|
|
|
|
|
|
2013-06-21 05:26:37 +08:00
|
|
|
config MMC_SDHCI_BCM_KONA
|
|
|
|
|
tristate "SDHCI support on Broadcom KONA platform"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_BCM_MOBILE || COMPILE_TEST
|
2014-06-06 05:14:41 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2013-06-21 05:26:37 +08:00
|
|
|
help
|
|
|
|
|
This selects the Broadcom Kona Secure Digital Host Controller
|
|
|
|
|
Interface(SDHCI) support.
|
|
|
|
|
This is used in Broadcom mobile SoCs.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
2015-01-20 16:05:18 +08:00
|
|
|
config MMC_SDHCI_F_SDH30
|
|
|
|
|
tristate "SDHCI support for Fujitsu Semiconductor F_SDH30"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
2018-01-08 23:44:19 +08:00
|
|
|
depends on OF || ACPI
|
2015-01-20 16:05:18 +08:00
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
Needed by some Fujitsu SoC for MMC / SD / SDIO support.
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2019-09-10 09:41:06 +08:00
|
|
|
config MMC_SDHCI_MILBEAUT
|
|
|
|
|
tristate "SDHCI support for Socionext Milbeaut Serieas using F_SDH30"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
Needed by Milbeaut SoC for MMC / SD / SDIO support.
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-02-10 08:06:30 +08:00
|
|
|
config MMC_SDHCI_IPROC
|
2016-01-28 06:25:41 +08:00
|
|
|
tristate "SDHCI support for the BCM2835 & iProc SD/MMC Controller"
|
2021-06-03 03:27:58 +08:00
|
|
|
depends on ARCH_BCM2835 || ARCH_BCM_IPROC || ARCH_BRCMSTB || COMPILE_TEST
|
2015-02-10 08:06:30 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2018-08-05 15:52:52 +08:00
|
|
|
depends on OF || ACPI
|
2015-02-10 08:06:30 +08:00
|
|
|
default ARCH_BCM_IPROC
|
|
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
|
|
|
|
help
|
|
|
|
|
This selects the iProc SD/MMC controller.
|
|
|
|
|
|
2016-01-28 06:25:41 +08:00
|
|
|
If you have a BCM2835 or IPROC platform with SD or MMC devices,
|
2015-02-10 08:06:30 +08:00
|
|
|
say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2016-10-20 02:18:24 +08:00
|
|
|
config MMC_MESON_GX
|
2018-04-03 18:06:51 +08:00
|
|
|
tristate "Amlogic S905/GX*/AXG SD/MMC Host Controller support"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_MESON|| COMPILE_TEST
|
2020-09-26 00:43:23 +08:00
|
|
|
depends on COMMON_CLK
|
2016-10-20 02:18:24 +08:00
|
|
|
help
|
|
|
|
|
This selects support for the Amlogic SD/MMC Host Controller
|
2018-04-03 18:06:51 +08:00
|
|
|
found on the S905/GX*/AXG family of SoCs. This controller is
|
2016-10-20 02:18:24 +08:00
|
|
|
MMC 5.1 compliant and supports SD, eMMC and SDIO interfaces.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y here.
|
|
|
|
|
|
2020-05-13 04:41:47 +08:00
|
|
|
config MMC_MESON_MX_SDHC
|
|
|
|
|
tristate "Amlogic Meson SDHC Host Controller support"
|
|
|
|
|
depends on (ARM && ARCH_MESON) || COMPILE_TEST
|
|
|
|
|
depends on COMMON_CLK
|
|
|
|
|
depends on OF
|
|
|
|
|
help
|
|
|
|
|
This selects support for the SDHC Host Controller on
|
|
|
|
|
Amlogic Meson6, Meson8, Meson8b and Meson8m2 SoCs.
|
|
|
|
|
The controller supports the SD/SDIO Spec 3.x and eMMC Spec 4.5x
|
|
|
|
|
with 1, 4, and 8 bit bus widths.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
mmc: meson-mx-sdio: Add a driver for the Amlogic Meson8 and Meson8b SoCs
Add a driver for the SDIO/MMC host found on the Amlogic Meson SoCs. This
is an MMC controller which provides an interface between the application
processor and various memory cards. It supports the SD specification
v2.0 and the eMMC specification v4.41.
The controller provides an internal "mux" which allows connecting up to
three MMC devices to it. Only one device can be used at a time though
since the registers are shared across all devices. The driver takes care
of synchronizing access (similar to the dw_mmc driver).
The maximum supported bus-width is 4-bits.
Amlogic's GPL kernel sources call the corresponding driver "aml_sdio" to
differentiate it from the other MMC controller in (at least the Meson8
and Meson8b) the SoCs (they call the other drivers aml_sdhc and
aml_sdhc_m8, which seem to support a bus-width of up to 8-bits). This
means that there are three different MMC host controller IP blocks from
Amlogic (each of them with completely own register layout and features):
- "SDIO": 1 and 4 bit bus width, support for high-speed modes up to
UHS-I SDR50, part of Meson6, Meson8 and Meson8b (the driver from this
patch targets this controller)
- "SDHC": 1, 4 and 8 bit bus width, compatible with standard iNAND
interface, support for speeds up to HS200 and MMC spec up to version
4.5x, part of Meson8 and Meson8b SoCs (there is no mainline driver
for this controller yet)
- "SDEMMC": 1, 4 and 8 bit bus width, support for speeds up to HS400
and MMC spec up to version 5.0, part of the Meson GX (64-bit) SoCs
(supported by the meson-gx MMC host driver)
Signed-off-by: Carlo Caione <carlo@endlessm.com>
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-03 19:24:17 +08:00
|
|
|
config MMC_MESON_MX_SDIO
|
|
|
|
|
tristate "Amlogic Meson6/Meson8/Meson8b SD/MMC Host Controller support"
|
|
|
|
|
depends on ARCH_MESON || COMPILE_TEST
|
|
|
|
|
depends on COMMON_CLK
|
2020-04-09 14:44:12 +08:00
|
|
|
depends on OF_ADDRESS
|
mmc: meson-mx-sdio: Add a driver for the Amlogic Meson8 and Meson8b SoCs
Add a driver for the SDIO/MMC host found on the Amlogic Meson SoCs. This
is an MMC controller which provides an interface between the application
processor and various memory cards. It supports the SD specification
v2.0 and the eMMC specification v4.41.
The controller provides an internal "mux" which allows connecting up to
three MMC devices to it. Only one device can be used at a time though
since the registers are shared across all devices. The driver takes care
of synchronizing access (similar to the dw_mmc driver).
The maximum supported bus-width is 4-bits.
Amlogic's GPL kernel sources call the corresponding driver "aml_sdio" to
differentiate it from the other MMC controller in (at least the Meson8
and Meson8b) the SoCs (they call the other drivers aml_sdhc and
aml_sdhc_m8, which seem to support a bus-width of up to 8-bits). This
means that there are three different MMC host controller IP blocks from
Amlogic (each of them with completely own register layout and features):
- "SDIO": 1 and 4 bit bus width, support for high-speed modes up to
UHS-I SDR50, part of Meson6, Meson8 and Meson8b (the driver from this
patch targets this controller)
- "SDHC": 1, 4 and 8 bit bus width, compatible with standard iNAND
interface, support for speeds up to HS200 and MMC spec up to version
4.5x, part of Meson8 and Meson8b SoCs (there is no mainline driver
for this controller yet)
- "SDEMMC": 1, 4 and 8 bit bus width, support for speeds up to HS400
and MMC spec up to version 5.0, part of the Meson GX (64-bit) SoCs
(supported by the meson-gx MMC host driver)
Signed-off-by: Carlo Caione <carlo@endlessm.com>
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-03 19:24:17 +08:00
|
|
|
help
|
|
|
|
|
This selects support for the SD/MMC Host Controller on
|
|
|
|
|
Amlogic Meson6, Meson8 and Meson8b SoCs.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2014-04-09 21:54:11 +08:00
|
|
|
config MMC_MOXART
|
|
|
|
|
tristate "MOXART SD/MMC Host Controller support"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_MOXART || COMPILE_TEST
|
2014-04-09 21:54:11 +08:00
|
|
|
help
|
|
|
|
|
This selects support for the MOXART SD/MMC Host Controller.
|
|
|
|
|
MOXA provides one multi-functional card reader which can
|
|
|
|
|
be found on some embedded hardware such as UC-7112-LX.
|
|
|
|
|
If you have a controller with this interface, say Y here.
|
|
|
|
|
|
2014-07-09 23:07:32 +08:00
|
|
|
config MMC_SDHCI_ST
|
|
|
|
|
tristate "SDHCI support on STMicroelectronics SoC"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_STI || FSP2 || COMPILE_TEST
|
2014-07-09 23:07:32 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
|
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface in
|
|
|
|
|
STMicroelectronics SoCs.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-02-12 02:57:36 +08:00
|
|
|
config MMC_OMAP
|
|
|
|
|
tristate "TI OMAP Multimedia Card Interface support"
|
2007-05-09 04:30:32 +08:00
|
|
|
depends on ARCH_OMAP
|
2014-06-06 05:14:40 +08:00
|
|
|
depends on TPS65010 || !MACH_OMAP_H2
|
2007-02-12 02:57:36 +08:00
|
|
|
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 08:05:23 +08:00
|
|
|
config MMC_OMAP_HS
|
|
|
|
|
tristate "TI OMAP High Speed Multimedia Card Interface support"
|
2015-10-21 05:50:06 +08:00
|
|
|
depends on ARCH_OMAP2PLUS || ARCH_KEYSTONE || COMPILE_TEST
|
2009-01-23 08:05:23 +08:00
|
|
|
help
|
|
|
|
|
This selects the TI OMAP High Speed Multimedia card Interface.
|
2013-07-11 00:06:24 +08:00
|
|
|
If you have an omap2plus board with a Multimedia Card slot,
|
|
|
|
|
say Y or M here.
|
2009-01-23 08:05:23 +08:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-02-12 02:57:36 +08:00
|
|
|
config MMC_WBSD
|
|
|
|
|
tristate "Winbond W83L51xD SD/MMC Card Interface support"
|
2007-05-09 04:30:32 +08:00
|
|
|
depends on ISA_DMA_API
|
2007-02-12 02:57:36 +08:00
|
|
|
help
|
|
|
|
|
This selects the Winbond(R) W83L51xD Secure digital and
|
2019-03-07 02:27:51 +08:00
|
|
|
Multimedia card Interface.
|
2007-02-12 02:57:36 +08:00
|
|
|
If you have a machine with a integrated W83L518D or W83L519D
|
|
|
|
|
SD/MMC card reader, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2018-12-02 18:30:46 +08:00
|
|
|
config MMC_ALCOR
|
|
|
|
|
tristate "Alcor Micro/Alcor Link SD/MMC controller"
|
|
|
|
|
depends on MISC_ALCOR_PCI
|
|
|
|
|
help
|
|
|
|
|
Say Y here to include driver code to support SD/MMC card interface
|
|
|
|
|
of Alcor Micro PCI-E card reader
|
|
|
|
|
|
2007-02-12 02:57:36 +08:00
|
|
|
config MMC_AU1X
|
|
|
|
|
tristate "Alchemy AU1XX0 MMC Card Interface support"
|
2011-08-12 17:39:45 +08:00
|
|
|
depends on MIPS_ALCHEMY
|
2007-02-12 02:57:36 +08: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.
|
|
|
|
|
|
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-07-01 00:35:03 +08:00
|
|
|
config MMC_ATMELMCI
|
2012-10-29 22:27:55 +08:00
|
|
|
tristate "Atmel SD/MMC Driver (Multimedia Card Interface)"
|
2017-05-10 01:21:17 +08:00
|
|
|
depends on 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-07-01 00:35:03 +08:00
|
|
|
help
|
2017-05-10 01:21:17 +08:00
|
|
|
This selects the Atmel Multimedia Card Interface driver.
|
|
|
|
|
If you have an 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-07-01 00:35:03 +08:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2014-03-10 23:37:12 +08:00
|
|
|
config MMC_SDHCI_MSM
|
|
|
|
|
tristate "Qualcomm SDHCI Controller Support"
|
2020-08-25 01:18:50 +08:00
|
|
|
depends on ARCH_QCOM || COMPILE_TEST
|
2014-03-10 23:37:12 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
2017-09-27 13:34:42 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2020-01-17 01:03:11 +08:00
|
|
|
select MMC_CQHCI
|
mmc: sdhci-msm: add Inline Crypto Engine support
Add support for Qualcomm Inline Crypto Engine (ICE) to sdhci-msm.
The standard-compliant parts, such as querying the crypto capabilities
and enabling crypto for individual MMC requests, are already handled by
cqhci-crypto.c, which itself is wired into the blk-crypto framework.
However, ICE requires vendor-specific init, enable, and resume logic,
and it requires that keys be programmed and evicted by vendor-specific
SMC calls. Make the sdhci-msm driver handle these details.
This is heavily inspired by the similar changes made for UFS, since the
UFS and eMMC ICE instances are very similar. See commit df4ec2fa7a4d
("scsi: ufs-qcom: Add Inline Crypto Engine support").
I tested this on a Sony Xperia 10, which uses the Snapdragon 630 SoC,
which has basic upstream support. Mainly, I used android-xfstests
(https://github.com/tytso/xfstests-bld/blob/master/Documentation/android-xfstests.md)
to run the ext4 and f2fs encryption tests in a Debian chroot:
android-xfstests -c ext4,f2fs -g encrypt -m inlinecrypt
These tests included tests which verify that the on-disk ciphertext is
identical to that produced by a software implementation. I also
verified that ICE was actually being used.
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
Reviewed-by: Satya Tangirala <satyat@google.com>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Link: https://lore.kernel.org/r/20210126001456.382989-9-ebiggers@kernel.org
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
2021-01-26 08:14:55 +08:00
|
|
|
select QCOM_SCM if MMC_CRYPTO && ARCH_QCOM
|
2014-03-10 23:37:12 +08:00
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
support present in Qualcomm SOCs. The controller supports
|
|
|
|
|
SD/MMC/SDIO devices.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-01-07 00:04:14 +08:00
|
|
|
config MMC_MXC
|
2013-04-09 05:28:06 +08:00
|
|
|
tristate "Freescale i.MX21/27/31 or MPC512x Multimedia Card support"
|
|
|
|
|
depends on ARCH_MXC || PPC_MPC512x
|
2009-01-07 00:04:14 +08:00
|
|
|
help
|
2013-04-09 05:28:06 +08:00
|
|
|
This selects the Freescale i.MX21, i.MX27, i.MX31 or MPC512x
|
|
|
|
|
Multimedia Card Interface. If you have an i.MX or MPC512x platform
|
|
|
|
|
with a Multimedia Card slot, say Y or M here.
|
2007-02-12 02:57:36 +08:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-02-21 18:35:28 +08:00
|
|
|
config MMC_MXS
|
|
|
|
|
tristate "Freescale MXS Multimedia Card Interface support"
|
|
|
|
|
depends on ARCH_MXS && MXS_DMA
|
|
|
|
|
help
|
|
|
|
|
This selects the Freescale SSP MMC controller found on MXS based
|
|
|
|
|
platforms like mx23/28.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-02-12 02:57:36 +08:00
|
|
|
config MMC_TIFM_SD
|
2012-10-03 02:17:47 +08:00
|
|
|
tristate "TI Flash Media MMC/SD Interface support"
|
|
|
|
|
depends on PCI
|
2007-02-12 02:57:36 +08: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)'.
|
|
|
|
|
|
2019-03-07 02:27:51 +08:00
|
|
|
To compile this driver as a module, choose M here: the
|
2007-02-12 02:57:36 +08:00
|
|
|
module will be called tifm_sd.
|
|
|
|
|
|
2009-02-14 16:07:26 +08:00
|
|
|
config MMC_MVSDIO
|
|
|
|
|
tristate "Marvell MMC/SD/SDIO host driver"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on PLAT_ORION || (COMPILE_TEST && ARM)
|
2015-11-25 21:57:57 +08:00
|
|
|
depends on OF
|
2020-06-14 00:50:22 +08:00
|
|
|
help
|
2009-02-14 16:07:26 +08:00
|
|
|
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 10:01:21 +08:00
|
|
|
config MMC_DAVINCI
|
2019-03-07 02:27:51 +08:00
|
|
|
tristate "TI DAVINCI Multimedia Card Interface support"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_DAVINCI || COMPILE_TEST
|
2019-03-07 02:27:51 +08:00
|
|
|
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.
|
2009-12-15 10:01:21 +08:00
|
|
|
|
2007-08-09 00:12:54 +08:00
|
|
|
config MMC_SPI
|
2008-09-07 19:16:58 +08:00
|
|
|
tristate "MMC/SD/SDIO over SPI"
|
2020-09-01 23:04:38 +08:00
|
|
|
depends on SPI_MASTER
|
2007-08-09 00:12:54 +08:00
|
|
|
select CRC7
|
|
|
|
|
select CRC_ITU_T
|
|
|
|
|
help
|
2009-01-26 18:12:25 +08:00
|
|
|
Some systems access MMC/SD/SDIO cards using a SPI controller
|
2008-09-07 19:16:58 +08: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-09 00:12:54 +08:00
|
|
|
|
|
|
|
|
If unsure, or if your system has no SPI master driver, say N.
|
|
|
|
|
|
2008-07-01 05:40:24 +08:00
|
|
|
config MMC_S3C
|
|
|
|
|
tristate "Samsung S3C SD/MMC Card Interface support"
|
2020-10-26 23:38:09 +08:00
|
|
|
depends on ARCH_S3C24XX || COMPILE_TEST
|
|
|
|
|
depends on S3C24XX_DMAC || COMPILE_TEST
|
2008-07-01 05:40:24 +08:00
|
|
|
help
|
|
|
|
|
This selects a driver for the MCI interface found in
|
2019-03-07 02:27:51 +08:00
|
|
|
Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs.
|
2008-07-01 05:40:24 +08:00
|
|
|
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 06:44:20 +08:00
|
|
|
config MMC_S3C_HW_SDIO_IRQ
|
2019-03-07 02:27:51 +08:00
|
|
|
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 06:44:20 +08:00
|
|
|
|
2009-10-02 06:44:18 +08: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
|
2012-10-03 02:17:47 +08:00
|
|
|
bool "Use DMA transfers only"
|
2009-10-02 06:44:18 +08:00
|
|
|
help
|
2020-11-14 20:08:19 +08:00
|
|
|
Use DMA to transfer data between memory and the hardware.
|
2009-10-02 06:44:18 +08:00
|
|
|
|
|
|
|
|
Currently, the DMA support in this driver seems to not be
|
|
|
|
|
working properly and needs to be debugged before this
|
|
|
|
|
option is useful.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2008-07-15 20:21:29 +08:00
|
|
|
config MMC_SDRICOH_CS
|
2012-10-03 02:17:47 +08:00
|
|
|
tristate "MMC/SD driver for Ricoh Bay1Controllers"
|
|
|
|
|
depends on PCI && PCMCIA
|
2008-07-15 20:21:29 +08: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.
|
|
|
|
|
|
2018-08-30 16:21:44 +08:00
|
|
|
config MMC_SDHCI_SPRD
|
|
|
|
|
tristate "Spreadtrum SDIO host Controller"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_SPRD || COMPILE_TEST
|
2018-08-30 16:21:44 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2020-02-12 12:13:00 +08:00
|
|
|
select MMC_HSQ
|
2018-08-30 16:21:44 +08:00
|
|
|
help
|
|
|
|
|
This selects the SDIO Host Controller in Spreadtrum
|
|
|
|
|
SoCs, this driver supports R11(IP version: R11P0).
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-03-23 19:42:44 +08:00
|
|
|
config MMC_TMIO_CORE
|
|
|
|
|
tristate
|
|
|
|
|
|
2008-07-15 23:02:21 +08:00
|
|
|
config MMC_TMIO
|
|
|
|
|
tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on MFD_TMIO || MFD_ASIC3 || COMPILE_TEST
|
2011-03-23 19:42:44 +08:00
|
|
|
select MMC_TMIO_CORE
|
2008-07-15 23:02:21 +08:00
|
|
|
help
|
|
|
|
|
This provides support for the SD/MMC cell found in TC6393XB,
|
2009-06-05 02:12:37 +08:00
|
|
|
T7L66XB and also HTC ASIC3
|
2009-05-23 02:33:59 +08:00
|
|
|
|
2011-03-14 16:52:33 +08:00
|
|
|
config MMC_SDHI
|
2017-05-10 17:25:29 +08:00
|
|
|
tristate "Renesas SDHI SD/SDIO controller support"
|
2016-02-24 10:39:33 +08:00
|
|
|
depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
|
2011-03-14 16:52:33 +08:00
|
|
|
select MMC_TMIO_CORE
|
2021-03-17 17:16:22 +08:00
|
|
|
select RESET_CONTROLLER if ARCH_RENESAS
|
2011-03-14 16:52:33 +08:00
|
|
|
help
|
|
|
|
|
This provides support for the SDHI SD/SDIO controller found in
|
2017-05-10 17:25:29 +08:00
|
|
|
Renesas SuperH, ARM and ARM64 based SoCs
|
2011-03-14 16:52:33 +08:00
|
|
|
|
2017-06-21 22:00:29 +08:00
|
|
|
config MMC_SDHI_SYS_DMAC
|
|
|
|
|
tristate "DMA for SDHI SD/SDIO controllers using SYS-DMAC"
|
2018-04-18 01:49:13 +08:00
|
|
|
depends on MMC_SDHI
|
2017-11-25 00:24:36 +08:00
|
|
|
default MMC_SDHI if (SUPERH || ARM)
|
2017-06-21 22:00:29 +08:00
|
|
|
help
|
|
|
|
|
This provides DMA support for SDHI SD/SDIO controllers
|
|
|
|
|
using SYS-DMAC via DMA Engine. This supports the controllers
|
|
|
|
|
found in SuperH and Renesas ARM based SoCs.
|
|
|
|
|
|
|
|
|
|
config MMC_SDHI_INTERNAL_DMAC
|
|
|
|
|
tristate "DMA for SDHI SD/SDIO controllers using on-chip bus mastering"
|
2018-10-25 06:23:00 +08:00
|
|
|
depends on ARM64 || ARCH_R7S9210 || ARCH_R8A77470 || COMPILE_TEST
|
2018-04-18 01:49:13 +08:00
|
|
|
depends on MMC_SDHI
|
2018-10-25 06:23:00 +08:00
|
|
|
default MMC_SDHI if (ARM64 || ARCH_R7S9210 || ARCH_R8A77470)
|
2017-06-21 22:00:29 +08:00
|
|
|
help
|
|
|
|
|
This provides DMA support for SDHI SD/SDIO controllers
|
|
|
|
|
using on-chip bus mastering. This supports the controllers
|
2018-10-25 06:23:00 +08:00
|
|
|
found in arm64 based SoCs. This controller is also found in
|
|
|
|
|
some RZ family SoCs.
|
2017-06-21 22:00:29 +08:00
|
|
|
|
mmc: uniphier-sd: add UniPhier SD/eMMC controller driver
Here is another TMIO MMC variant found in Socionext UniPhier SoCs.
As commit b6147490e6aa ("mmc: tmio: split core functionality, DMA and
MFD glue") said, these MMC controllers use the IP from Panasonic.
However, the MMC controller in the TMIO (Toshiba Mobile IO) MFD chip
was the first upstreamed user of this IP. The common driver code
for this IP is now called 'tmio-mmc-core' in Linux although it is a
historical misnomer.
Anyway, this driver select's MMC_TMIO_CORE to borrow the common code
from tmio-mmc-core.c
Older UniPhier SoCs (LD4, Pro4, sLD8) support the external DMA engine
like renesas_sdhi_sys_dmac.c. The difference is UniPhier SoCs use a
single DMA channel whereas Renesas chips request separate channels for
RX and TX.
Newer UniPhier SoCs (Pro5 and later) support the internal DMA engine
like renesas_sdhi_internal_dmac.c The register map is almost the same,
so I guess Renesas and Socionext use the same internal DMA hardware.
The main difference is, the register offsets are doubled for Renesas.
Renesas Socionext
SDHI UniPhier
DM_CM_DTRAN_MODE 0x820 0x410
DM_CM_DTRAN_CTRL 0x828 0x414
DM_CM_RST 0x830 0x418
DM_CM_INFO1 0x840 0x420
DM_CM_INFO1_MASK 0x848 0x424
DM_CM_INFO2 0x850 0x428
DM_CM_INFO2_MASK 0x858 0x42c
DM_DTRAN_ADDR 0x880 0x440
DM_DTRAN_ADDREX --- 0x444
This comes from the difference of host->bus_shift; 2 for Renesas SoCs,
and 1 for UniPhier SoCs. Also, the datasheet for UniPhier SoCs defines
DM_DTRAN_ADDR and DM_DTRAN_ADDREX as two separate registers.
It could be possible to factor out the DMA common code by introducing
some hooks to cope with platform quirks, but this patch does not touch
that for now.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
2018-08-23 12:44:18 +08:00
|
|
|
config MMC_UNIPHIER
|
|
|
|
|
tristate "UniPhier SD/eMMC Host Controller support"
|
|
|
|
|
depends on ARCH_UNIPHIER || COMPILE_TEST
|
|
|
|
|
depends on OF
|
|
|
|
|
select MMC_TMIO_CORE
|
|
|
|
|
help
|
|
|
|
|
This provides support for the SD/eMMC controller found in
|
|
|
|
|
UniPhier SoCs. The eMMC variant of this controller is used
|
|
|
|
|
only for 32-bit SoCs.
|
|
|
|
|
|
2009-05-23 02:33:59 +08:00
|
|
|
config MMC_CB710
|
|
|
|
|
tristate "ENE CB710 MMC/SD Interface support"
|
2013-08-30 15:39:53 +08:00
|
|
|
depends on PCI
|
2009-05-23 02:33:59 +08:00
|
|
|
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-18 02:22:39 +08: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 10:01:32 +08:00
|
|
|
|
2017-04-25 02:41:57 +08:00
|
|
|
config MMC_CAVIUM_OCTEON
|
|
|
|
|
tristate "Cavium OCTEON SD/MMC Card Interface support"
|
|
|
|
|
depends on CAVIUM_OCTEON_SOC
|
|
|
|
|
help
|
|
|
|
|
This selects Cavium OCTEON SD/MMC card Interface.
|
|
|
|
|
If you have an OCTEON board with a Multimedia Card slot,
|
|
|
|
|
say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2017-03-30 23:31:25 +08:00
|
|
|
config MMC_CAVIUM_THUNDERX
|
|
|
|
|
tristate "Cavium ThunderX SD/MMC Card Interface support"
|
|
|
|
|
depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
|
2017-10-02 20:02:41 +08:00
|
|
|
depends on GPIO_THUNDERX
|
2017-03-30 23:31:25 +08:00
|
|
|
depends on OF_ADDRESS
|
|
|
|
|
help
|
|
|
|
|
This selects Cavium ThunderX SD/MMC Card Interface.
|
|
|
|
|
If you have an Cavium ARM64 board with a Multimedia Card slot
|
|
|
|
|
or builtin eMMC chip say Y or M here. If built as a module
|
|
|
|
|
the module will be called thunderx_mmc.ko.
|
|
|
|
|
|
2011-01-02 14:11:59 +08:00
|
|
|
config MMC_DW
|
|
|
|
|
tristate "Synopsys DesignWare Memory Card Interface"
|
2020-08-08 19:45:02 +08:00
|
|
|
depends on ARC || ARM || ARM64 || MIPS || RISCV || CSKY || COMPILE_TEST
|
2011-01-02 14:11:59 +08:00
|
|
|
help
|
|
|
|
|
This selects support for the Synopsys DesignWare Mobile Storage IP
|
|
|
|
|
block, this provides host support for SD and MMC interfaces, in both
|
2015-09-16 14:41:23 +08:00
|
|
|
PIO, internal DMA mode and external DMA mode.
|
2011-01-02 14:11:59 +08:00
|
|
|
|
2012-01-13 18:34:57 +08:00
|
|
|
config MMC_DW_PLTFM
|
|
|
|
|
tristate "Synopsys Designware MCI Support as platform device"
|
|
|
|
|
depends on MMC_DW
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This selects the common helper functions support for Host Controller
|
|
|
|
|
Interface based platform driver. Please select this option if the IP
|
|
|
|
|
is present as a platform device. This is the common interface for the
|
|
|
|
|
Synopsys Designware IP.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2018-05-09 02:46:48 +08:00
|
|
|
config MMC_DW_BLUEFIELD
|
|
|
|
|
tristate "BlueField specific extensions for Synopsys DW Memory Card Interface"
|
|
|
|
|
depends on MMC_DW
|
|
|
|
|
select MMC_DW_PLTFM
|
|
|
|
|
help
|
|
|
|
|
This selects support for Mellanox BlueField SoC specific extensions to
|
|
|
|
|
the Synopsys DesignWare Memory Card Interface driver. Select this
|
|
|
|
|
option for platforms based on Mellanox BlueField SoC's.
|
|
|
|
|
|
2012-09-18 02:16:43 +08:00
|
|
|
config MMC_DW_EXYNOS
|
2012-11-30 15:44:39 +08:00
|
|
|
tristate "Exynos specific extensions for Synopsys DW Memory Card Interface"
|
2012-09-18 02:16:43 +08:00
|
|
|
depends on MMC_DW
|
|
|
|
|
select MMC_DW_PLTFM
|
|
|
|
|
help
|
|
|
|
|
This selects support for Samsung Exynos SoC specific extensions to the
|
|
|
|
|
Synopsys DesignWare Memory Card Interface driver. Select this option
|
|
|
|
|
for platforms based on Exynos4 and Exynos5 SoC's.
|
|
|
|
|
|
2018-03-08 09:01:34 +08:00
|
|
|
config MMC_DW_HI3798CV200
|
|
|
|
|
tristate "Hi3798CV200 specific extensions for Synopsys DW Memory Card Interface"
|
|
|
|
|
depends on MMC_DW
|
|
|
|
|
select MMC_DW_PLTFM
|
|
|
|
|
help
|
|
|
|
|
This selects support for HiSilicon Hi3798CV200 SoC specific extensions to the
|
|
|
|
|
Synopsys DesignWare Memory Card Interface driver. Select this option
|
|
|
|
|
for platforms based on HiSilicon Hi3798CV200 SoC.
|
|
|
|
|
|
2014-01-09 22:35:11 +08:00
|
|
|
config MMC_DW_K3
|
|
|
|
|
tristate "K3 specific extensions for Synopsys DW Memory Card Interface"
|
|
|
|
|
depends on MMC_DW
|
|
|
|
|
select MMC_DW_PLTFM
|
|
|
|
|
help
|
|
|
|
|
This selects support for Hisilicon K3 SoC specific extensions to the
|
|
|
|
|
Synopsys DesignWare Memory Card Interface driver. Select this option
|
|
|
|
|
for platforms based on Hisilicon K3 SoC's.
|
|
|
|
|
|
2012-01-13 18:34:57 +08:00
|
|
|
config MMC_DW_PCI
|
|
|
|
|
tristate "Synopsys Designware MCI support on PCI bus"
|
|
|
|
|
depends on MMC_DW && PCI
|
|
|
|
|
help
|
|
|
|
|
This selects the PCI bus for the Synopsys Designware Mobile Storage IP.
|
|
|
|
|
Select this option if the IP is present on PCI platform.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2014-08-19 12:36:14 +08:00
|
|
|
config MMC_DW_ROCKCHIP
|
|
|
|
|
tristate "Rockchip specific extensions for Synopsys DW Memory Card Interface"
|
|
|
|
|
depends on MMC_DW && ARCH_ROCKCHIP
|
|
|
|
|
select MMC_DW_PLTFM
|
|
|
|
|
help
|
|
|
|
|
This selects support for Rockchip SoC specific extensions to the
|
|
|
|
|
Synopsys DesignWare Memory Card Interface driver. Select this option
|
|
|
|
|
for platforms based on RK3066, RK3188 and RK3288 SoC's.
|
|
|
|
|
|
2010-05-27 05:41:59 +08:00
|
|
|
config MMC_SH_MMCIF
|
|
|
|
|
tristate "SuperH Internal MMCIF support"
|
2016-02-24 10:39:33 +08:00
|
|
|
depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
|
2010-05-27 05:41:59 +08:00
|
|
|
help
|
2016-04-27 04:34:46 +08:00
|
|
|
This selects the MMC Host Interface controller (MMCIF) found in various
|
|
|
|
|
Renesas SoCs for SH and ARM architectures.
|
2010-05-27 05:41:59 +08:00
|
|
|
|
2010-07-16 04:06:04 +08:00
|
|
|
|
|
|
|
|
config MMC_JZ4740
|
2018-03-29 05:00:51 +08:00
|
|
|
tristate "Ingenic JZ47xx SD/Multimedia Card Interface support"
|
2018-08-21 21:03:20 +08:00
|
|
|
depends on MIPS
|
2010-07-16 04:06:04 +08:00
|
|
|
help
|
2018-03-29 05:00:51 +08:00
|
|
|
This selects support for the SD/MMC controller on Ingenic
|
|
|
|
|
JZ4740, JZ4750, JZ4770 and JZ4780 SoCs.
|
|
|
|
|
|
2010-07-16 04:06:04 +08:00
|
|
|
If you have a board based on such a SoC and with a SD/MMC slot,
|
|
|
|
|
say Y or M here.
|
2010-09-02 22:15:08 +08:00
|
|
|
|
2011-05-15 04:48:13 +08:00
|
|
|
config MMC_VUB300
|
|
|
|
|
tristate "VUB300 USB to SDIO/SD/MMC Host Controller support"
|
|
|
|
|
depends on USB
|
|
|
|
|
help
|
|
|
|
|
This selects support for Elan Digital Systems' VUB300 chip.
|
|
|
|
|
|
|
|
|
|
The VUB300 is a USB-SDIO Host Controller Interface chip
|
|
|
|
|
that enables the host computer to use SDIO/SD/MMC cards
|
|
|
|
|
via a USB 2.0 or USB 1.1 host.
|
|
|
|
|
|
|
|
|
|
The VUB300 chip will be found in both physically separate
|
|
|
|
|
USB to SDIO/SD/MMC adapters and embedded on some motherboards.
|
|
|
|
|
|
|
|
|
|
The VUB300 chip supports SD and MMC memory cards in addition
|
|
|
|
|
to single and multifunction SDIO cards.
|
|
|
|
|
|
|
|
|
|
Some SDIO cards will need a firmware file to be loaded and
|
|
|
|
|
sent to VUB300 chip in order to achieve better data throughput.
|
|
|
|
|
Download these "Offload Pseudocode" from Elan Digital Systems'
|
|
|
|
|
web-site http://www.elandigitalsystems.com/support/downloads.php
|
|
|
|
|
and put them in /lib/firmware. Note that without these additional
|
|
|
|
|
firmware files the VUB300 chip will still function, but not at
|
|
|
|
|
the best obtainable data rate.
|
|
|
|
|
|
|
|
|
|
To compile this mmc host controller driver as a module,
|
|
|
|
|
choose M here: the module will be called vub300.
|
|
|
|
|
|
|
|
|
|
If you have a computer with an embedded VUB300 chip
|
|
|
|
|
or if you intend connecting a USB adapter based on a
|
|
|
|
|
VUB300 chip say Y or M here.
|
|
|
|
|
|
2010-09-02 22:15:08 +08:00
|
|
|
config MMC_USHC
|
|
|
|
|
tristate "USB SD Host Controller (USHC) support"
|
|
|
|
|
depends on USB
|
|
|
|
|
help
|
|
|
|
|
This selects support for USB SD Host Controllers based on
|
|
|
|
|
the Cypress Astoria chip with firmware compliant with CSR's
|
|
|
|
|
USB SD Host Controller specification (CS-118793-SP).
|
|
|
|
|
|
|
|
|
|
CSR boards with this device include: USB<>SDIO (M1985v2),
|
|
|
|
|
and Ultrasira.
|
|
|
|
|
|
|
|
|
|
Note: These controllers only support SDIO cards and do not
|
|
|
|
|
support MMC or SD memory cards.
|
2012-11-18 10:33:06 +08:00
|
|
|
|
|
|
|
|
config MMC_WMT
|
|
|
|
|
tristate "Wondermedia SD/MMC Host Controller support"
|
|
|
|
|
depends on ARCH_VT8500
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This selects support for the SD/MMC Host Controller on
|
|
|
|
|
Wondermedia WM8505/WM8650 based SoCs.
|
|
|
|
|
|
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
|
|
|
module will be called wmt-sdmmc.
|
Char/Misc driver merge for 3.8-rc1
Here is the "big" char/misc driver patches for 3.8-rc1. I'm starting to
put random driver subsystems that I had previously sent you through the
driver-core tree in this tree, as it makes more sense to do so.
Nothing major here, the various __dev* removals, some mei driver
updates, and other random driver-specific things from the different
maintainers and developers.
Note, some MFD drivers got added through this tree, and they are also
coming in through the "real" MFD tree as well, due to some major
mis-communication between me and the different developers. If you have
any merge conflicts, take the ones from the MFD tree, not these ones,
sorry about that.
All of this has been in linux-next for a while.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEABECAAYFAlDHj7AACgkQMUfUDdst+ym7pQCgxhFDGQRJimG+Ddag+ghfLhQh
Ql0AoJsWVFvQjb7q1NO7OvOABaxjEJdu
=na5b
-----END PGP SIGNATURE-----
Merge tag 'char-misc-3.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc
Pull Char/Misc driver merge from Greg Kroah-Hartman:
"Here is the "big" char/misc driver patches for 3.8-rc1. I'm starting
to put random driver subsystems that I had previously sent you through
the driver-core tree in this tree, as it makes more sense to do so.
Nothing major here, the various __dev* removals, some mei driver
updates, and other random driver-specific things from the different
maintainers and developers.
Note, some MFD drivers got added through this tree, and they are also
coming in through the "real" MFD tree as well, due to some major
mis-communication between me and the different developers. If you
have any merge conflicts, take the ones from the MFD tree, not these
ones, sorry about that.
All of this has been in linux-next for a while.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>"
Fix up trivial conflict in drivers/mmc/host/Kconfig due to new drivers
having been added (both at the end, as usual..)
* tag 'char-misc-3.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc: (84 commits)
MAINTAINERS: remove drivers/staging/hv/
misc/st_kim: Free resources in the error path of probe()
drivers/char: for hpet, add count checking, and ~0UL instead of -1
w1-gpio: Simplify & get rid of defines
w1-gpio: Pinctrl-fy
extcon: remove use of __devexit_p
extcon: remove use of __devinit
extcon: remove use of __devexit
drivers: uio: Only allocate new private data when probing device tree node
drivers: uio_dmem_genirq: Allow partial success when opening device
drivers: uio_dmem_genirq: Don't use DMA_ERROR_CODE to indicate unmapped regions
drivers: uio_dmem_genirq: Don't mix address spaces for dynamic region vaddr
uio: remove use of __devexit
uio: remove use of __devinitdata
uio: remove use of __devinit
uio: remove use of __devexit_p
char: remove use of __devexit
char: remove use of __devinitconst
char: remove use of __devinitdata
char: remove use of __devinit
...
2012-12-12 05:56:38 +08:00
|
|
|
|
2014-06-01 02:38:51 +08:00
|
|
|
config MMC_USDHI6ROL0
|
|
|
|
|
tristate "Renesas USDHI6ROL0 SD/SDIO Host Controller support"
|
2014-07-10 02:52:42 +08:00
|
|
|
depends on HAS_DMA
|
2014-06-01 02:38:51 +08:00
|
|
|
help
|
|
|
|
|
This selects support for the Renesas USDHI6ROL0 SD/SDIO
|
|
|
|
|
Host Controller
|
|
|
|
|
|
2012-11-09 20:53:34 +08:00
|
|
|
config MMC_REALTEK_PCI
|
|
|
|
|
tristate "Realtek PCI-E SD/MMC Card Interface Driver"
|
2017-11-29 17:08:03 +08:00
|
|
|
depends on MISC_RTSX_PCI
|
2012-11-09 20:53:34 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to include driver code to support SD/MMC card interface
|
|
|
|
|
of Realtek PCI-E card reader
|
2014-04-11 14:53:22 +08:00
|
|
|
|
|
|
|
|
config MMC_REALTEK_USB
|
|
|
|
|
tristate "Realtek USB SD/MMC Card Interface Driver"
|
2017-11-29 17:08:03 +08:00
|
|
|
depends on MISC_RTSX_USB
|
2014-04-11 14:53:22 +08:00
|
|
|
help
|
|
|
|
|
Say Y here to include driver code to support SD/MMC card interface
|
|
|
|
|
of Realtek RTS5129/39 series card reader
|
2014-05-12 20:04:48 +08:00
|
|
|
|
|
|
|
|
config MMC_SUNXI
|
|
|
|
|
tristate "Allwinner sunxi SD/MMC Host Controller support"
|
2020-09-07 18:52:54 +08:00
|
|
|
depends on ARCH_SUNXI || COMPILE_TEST
|
2014-05-12 20:04:48 +08:00
|
|
|
help
|
|
|
|
|
This selects support for the SD/MMC Host Controller on
|
|
|
|
|
Allwinner sunxi SoCs.
|
2014-11-12 00:54:55 +08:00
|
|
|
|
2017-11-29 21:41:05 +08:00
|
|
|
config MMC_CQHCI
|
|
|
|
|
tristate "Command Queue Host Controller Interface support"
|
|
|
|
|
depends on HAS_DMA
|
|
|
|
|
help
|
|
|
|
|
This selects the Command Queue Host Controller Interface (CQHCI)
|
|
|
|
|
support present in host controllers of Qualcomm Technologies, Inc
|
|
|
|
|
amongst others.
|
|
|
|
|
This controller supports eMMC devices with command queue support.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
mmc: Add MMC host software queue support
Now the MMC read/write stack will always wait for previous request is
completed by mmc_blk_rw_wait(), before sending a new request to hardware,
or queue a work to complete request, that will bring context switching
overhead and spend some extra time to poll the card for busy completion
for I/O writes via sending CMD13, especially for high I/O per second
rates, to affect the IO performance.
Thus this patch introduces MMC software queue interface based on the
hardware command queue engine's interfaces, which is similar with the
hardware command queue engine's idea, that can remove the context
switching. Moreover we set the default queue depth as 64 for software
queue, which allows more requests to be prepared, merged and inserted
into IO scheduler to improve performance, but we only allow 2 requests
in flight, that is enough to let the irq handler always trigger the
next request without a context switch, as well as avoiding a long latency.
Moreover the host controller should support HW busy detection for I/O
operations when enabling the host software queue. That means, the host
controller must not complete a data transfer request, until after the
card stops signals busy.
From the fio testing data in cover letter, we can see the software
queue can improve some performance with 4K block size, increasing
about 16% for random read, increasing about 90% for random write,
though no obvious improvement for sequential read and write.
Moreover we can expand the software queue interface to support MMC
packed request or packed command in future.
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
Signed-off-by: Baolin Wang <baolin.wang7@gmail.com>
Link: https://lore.kernel.org/r/4409c1586a9b3ed20d57ad2faf6c262fc3ccb6e2.1581478568.git.baolin.wang7@gmail.com
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
2020-02-12 12:12:56 +08:00
|
|
|
config MMC_HSQ
|
|
|
|
|
tristate "MMC Host Software Queue support"
|
|
|
|
|
help
|
|
|
|
|
This selects the MMC Host Software Queue support. This may increase
|
|
|
|
|
performance, if the host controller and its driver supports it.
|
|
|
|
|
|
|
|
|
|
If you have a controller/driver supporting this interface, say Y or M
|
|
|
|
|
here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2014-11-12 00:54:55 +08:00
|
|
|
config MMC_TOSHIBA_PCI
|
|
|
|
|
tristate "Toshiba Type A SD/MMC Card Interface Driver"
|
|
|
|
|
depends on PCI
|
2015-06-15 19:20:48 +08:00
|
|
|
|
2017-03-08 17:19:03 +08:00
|
|
|
config MMC_BCM2835
|
|
|
|
|
tristate "Broadcom BCM2835 SDHOST MMC Controller support"
|
|
|
|
|
depends on ARCH_BCM2835 || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
This selects the BCM2835 SDHOST MMC controller. If you have
|
|
|
|
|
a BCM2835 platform with SD or MMC devices, say Y or M here.
|
|
|
|
|
|
|
|
|
|
Note that the BCM2835 has two SD controllers: The Arasan
|
|
|
|
|
sdhci controller (supported by MMC_SDHCI_IPROC) and a custom
|
|
|
|
|
sdhost controller (supported by this driver).
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-06-15 19:20:48 +08:00
|
|
|
config MMC_MTK
|
|
|
|
|
tristate "MediaTek SD/MMC Card Interface support"
|
2015-06-26 20:09:26 +08:00
|
|
|
depends on HAS_DMA
|
2020-11-22 20:00:56 +08:00
|
|
|
depends on COMMON_CLK
|
2019-05-04 18:24:57 +08:00
|
|
|
select REGULATOR
|
2020-07-20 08:42:38 +08:00
|
|
|
select MMC_CQHCI
|
2015-06-15 19:20:48 +08:00
|
|
|
help
|
|
|
|
|
This selects the MediaTek(R) Secure digital and Multimedia card Interface.
|
|
|
|
|
If you have a machine with a integrated SD/MMC card reader, say Y or M here.
|
|
|
|
|
This is needed if support for any SD/SDIO/MMC devices is required.
|
|
|
|
|
If unsure, say N.
|
2016-01-14 09:15:45 +08:00
|
|
|
|
|
|
|
|
config MMC_SDHCI_MICROCHIP_PIC32
|
2019-03-07 02:27:51 +08:00
|
|
|
tristate "Microchip PIC32MZDA SDHCI support"
|
|
|
|
|
depends on MMC_SDHCI && PIC32MZDA && MMC_SDHCI_PLTFM
|
|
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
for PIC32MZDA platform.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
2016-01-14 09:15:45 +08:00
|
|
|
|
2019-03-07 02:27:51 +08:00
|
|
|
If unsure, say N.
|
2016-01-14 09:15:45 +08:00
|
|
|
|
2016-06-17 00:47:16 +08:00
|
|
|
config MMC_SDHCI_BRCMSTB
|
|
|
|
|
tristate "Broadcom SDIO/SD/MMC support"
|
|
|
|
|
depends on ARCH_BRCMSTB || BMIPS_GENERIC
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
2020-01-14 05:07:05 +08:00
|
|
|
select MMC_CQHCI
|
2016-06-17 00:47:16 +08:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This selects support for the SDIO/SD/MMC Host Controller on
|
|
|
|
|
Broadcom STB SoCs.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2017-03-30 23:22:59 +08:00
|
|
|
|
|
|
|
|
config MMC_SDHCI_XENON
|
|
|
|
|
tristate "Marvell Xenon eMMC/SD/SDIO SDHCI driver"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM
|
|
|
|
|
help
|
|
|
|
|
This selects Marvell Xenon eMMC/SD/SDIO SDHCI.
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
If unsure, say N.
|
2017-09-06 19:45:55 +08:00
|
|
|
|
|
|
|
|
config MMC_SDHCI_OMAP
|
|
|
|
|
tristate "TI SDHCI Controller Support"
|
|
|
|
|
depends on MMC_SDHCI_PLTFM && OF
|
2018-12-11 22:22:53 +08:00
|
|
|
select THERMAL
|
2019-01-09 20:43:12 +08:00
|
|
|
imply TI_SOC_THERMAL
|
2020-01-16 18:51:48 +08:00
|
|
|
select MMC_SDHCI_EXTERNAL_DMA if DMA_ENGINE
|
2017-09-06 19:45:55 +08:00
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
support present in TI's DRA7 SOCs. The controller supports
|
|
|
|
|
SD/MMC/SDIO devices.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2018-12-11 02:35:07 +08:00
|
|
|
|
|
|
|
|
config MMC_SDHCI_AM654
|
|
|
|
|
tristate "Support for the SDHCI Controller in TI's AM654 SOCs"
|
2019-07-02 21:36:31 +08:00
|
|
|
depends on MMC_SDHCI_PLTFM && OF && REGMAP_MMIO
|
2019-04-01 20:58:04 +08:00
|
|
|
select MMC_SDHCI_IO_ACCESSORS
|
2019-11-18 15:36:09 +08:00
|
|
|
select MMC_CQHCI
|
2018-12-11 02:35:07 +08:00
|
|
|
help
|
|
|
|
|
This selects the Secure Digital Host Controller Interface (SDHCI)
|
|
|
|
|
support present in TI's AM654 SOCs. The controller supports
|
|
|
|
|
SD/MMC/SDIO devices.
|
|
|
|
|
|
|
|
|
|
If you have a controller with this interface, say Y or M here.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2019-09-16 23:45:44 +08:00
|
|
|
|
|
|
|
|
config MMC_OWL
|
|
|
|
|
tristate "Actions Semi Owl SD/MMC Host Controller support"
|
|
|
|
|
depends on HAS_DMA
|
|
|
|
|
depends on ARCH_ACTIONS || COMPILE_TEST
|
|
|
|
|
help
|
|
|
|
|
This selects support for the SD/MMC Host Controller on
|
|
|
|
|
Actions Semi Owl SoCs.
|
2020-01-16 18:51:47 +08:00
|
|
|
|
|
|
|
|
config MMC_SDHCI_EXTERNAL_DMA
|
|
|
|
|
bool
|