Home
last modified time | relevance | path

Searched refs:MMC (Results 1 – 25 of 65) sorted by relevance

123

/linux-3.4.99/drivers/mmc/
DKconfig2 # MMC subsystem configuration
5 menuconfig MMC config
6 tristate "MMC/SD/SDIO card support"
12 If you want MMC/SD/SDIO support, you should say Y here and
16 bool "MMC debugging"
17 depends on MMC != n
20 say N here. This enables MMC core and driver debugging.
22 if MMC
30 endif # MMC
/linux-3.4.99/Documentation/mmc/
Dmmc-async-req.txt8 transfer, the DMA preparation overhead would not affect the MMC performance.
9 The intention of non-blocking (asynchronous) MMC requests is to minimize the
10 time between when an MMC request ends and another MMC request begins.
11 Using mmc_wait_for_req(), the MMC controller is idle while dma_map_sg and
12 dma_unmap_sg are processing. Using non-blocking MMC requests makes it
14 MMC request.
16 MMC block driver
19 The mmc_blk_issue_rw_rq() in the MMC block driver is made non-blocking.
22 a request and how fast the memory is. The faster the MMC/SD is the
34 MMC core API extension
[all …]
Dmmc-dev-parts.txt1 SD and MMC Device Partitions
5 SD/MMC device.
7 As of this writing, MMC boot partitions as supported and exposed as
11 MMC Boot Partitions
14 Read and write access is provided to the two MMC boot partitions. Due to
Dmmc-dev-attrs.txt1 SD and MMC Block Device Attributes
5 SD or MMC device.
11 SD and MMC Device Attributes
32 operation. For MMC, "erase_size" is the erase group size
38 SD/MMC cards can erase an arbitrarily large area up to and
59 For MMC, "preferred_erase_size" is the high-capacity
68 SD/MMC/SDIO Clock Gating Attribute
D00-INDEX4 - info on SD and MMC device attributes
6 - info on SD and MMC device partitions
/linux-3.4.99/drivers/mmc/core/
DKconfig2 # MMC core configuration
6 bool "Assume MMC/SD cards are non-removable (DANGEROUS)"
8 If you say Y here, the MMC layer will assume that all cards
15 a MMC/SD card for rootfs. Most people should say N here.
21 bool "MMC host clock gating (EXPERIMENTAL)"
24 This will attempt to aggressively gate the clock to the MMC card.
26 noise when the MMC card is not in use. Your host driver has to
/linux-3.4.99/drivers/mmc/host/
DKconfig2 # MMC/SD host controller drivers
5 comment "MMC/SD/SDIO Host Controller Drivers"
72 bool "Ricoh MMC Controller Disabler (EXPERIMENTAL)"
75 This adds a pci quirk to disable Ricoh MMC Controller. This
77 supports MMC cards on the SD controller, but if it is not
78 disabled, it will steal the MMC cards away - rendering them
159 tristate "SDHCI platform support for the Tegra SD/MMC Controller"
164 This selects the Tegra SD/MMC controller. If you have a Tegra
165 platform with SD or MMC devices, say Y or M here.
254 tristate "Winbond W83L51xD SD/MMC Card Interface support"
[all …]
/linux-3.4.99/drivers/mmc/card/
DKconfig2 # MMC/SD card drivers
5 comment "MMC/SD/SDIO Card Drivers"
8 tristate "MMC block device driver"
12 Say Y here to enable the MMC block device driver support.
14 mount the filesystem. Almost everyone wishing MMC support
26 Number of total MMC minors available is 256, so your number
40 SD/MMC is a high latency protocol where it is crucial to
60 tristate "MMC host test driver"
/linux-3.4.99/Documentation/arm/SH-Mobile/
Dzboot-rom-mmcif.txt1 ROM-able zImage boot from MMC
4 An ROM-able zImage compiled with ZBOOT_ROM_MMCIF may be written to MMC and
23 The zImage must be written to the MMC card at sector 1 (512 bytes) in
29 A dual-voltage MMC 4.0 card was used for testing.
/linux-3.4.99/Documentation/devicetree/bindings/mmc/
Dnvidia-sdhci.txt3 This controller on Tegra family SoCs provides an interface for MMC, SD,
8 - reg : Should contain SD/MMC registers location and length
9 - interrupts : Should contain SD/MMC interrupt
Dti-omap-hsmmc.txt1 * TI Highspeed MMC host controller for OMAP
3 The Highspeed MMC Host Controller on TI OMAP family
4 provides an interface for MMC, SD, and SDIO types of memory cards.
/linux-3.4.99/arch/sh/kernel/cpu/sh3/
Dsetup-sh7720.c415 SIOF0, SIOF1, MMC, PCC, enumerator
444 INTC_VECT(MMC, 0xe80), INTC_VECT(MMC, 0xea0),
445 INTC_VECT(MMC, 0xec0), INTC_VECT(MMC, 0xee0),
459 { 0xA4080006UL, 0, 16, 4, /* IPRI */ { SIOF0, SIOF1, MMC, PCC } },
/linux-3.4.99/drivers/staging/rts5139/
DTODO6 - This driver contains an entire SD/MMC stack -- it should use the stack in
9 - This driver presents cards as SCSI devices, but they should be MMC devices.
/linux-3.4.99/drivers/staging/rts_pstor/
DTODO6 - This driver contains an entire SD/MMC stack -- it should use the stack in
9 - This driver presents cards as SCSI devices, but they should be MMC devices.
/linux-3.4.99/drivers/net/wimax/i2400m/
DKconfig10 comment "Enable MMC support to see WiMAX SDIO drivers"
11 depends on MMC = n
26 depends on WIMAX && MMC
/linux-3.4.99/arch/cris/arch-v32/drivers/
DKconfig648 tristate "MMC/SD host driver using IO-processor"
649 depends on ETRAX_ARCH_V32 && MMC
651 This option enables the SD/MMC host controller interface.
657 # suggested uniquely) when an IOP driver emerges for "real" MMC/SD
661 default MMC
675 # for the board-info file until a separate non-MMC SPI board file
678 # configure non-MMC SPI ports together with MMC_SPI ports (if multiple
707 Say Y for an MMC/SD socket connected to synchronous serial port 0,
710 (You need to select MMC separately.)
721 string "MMC/SD card detect pin for SPI on sser0"
[all …]
/linux-3.4.99/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt87 MMC/SD/SDIO
90 No current support for the MMC/SD/SDIO block.
/linux-3.4.99/arch/arm/mach-s3c64xx/
DKconfig170 # for the MMC/SD slots connected to the same input. This means that
175 prompt "SMDK6410 MMC/SD slot setup"
182 Select CON7 (channel 0) as the MMC/SD slot, as
191 Select CON6 (channel 1) as the MMC/SD slot, as
/linux-3.4.99/arch/arm/mach-cns3xxx/
DKconfig11 for USB, USB-OTG, MMC/SD/SDIO, SATA, PCI-E, etc.
/linux-3.4.99/Documentation/spi/
Dep93xx_spi15 arch/arm/mach-ep93xx/*.c). In this example we configure MMC over SPI through
18 This example uses EGPIO9 as SD/MMC card chip select (this is wired in DIO1
/linux-3.4.99/arch/sh/kernel/cpu/sh4a/
Dsetup-sh7366.c346 DMAC0123, VIOVOU, MMC, DMAC45, FLCTL, I2C, enumerator
383 INTC_GROUP(MMC, MMC_MMC1I, MMC_MMC2I, MMC_MMC3I),
431 { 0xa4080028, 0, 16, 4, /* IPRK */ { 0, MMC, 0, SDHI } },
Dsetup-sh7343.c394 DMAC0123, VIOVOU, MMC, DMAC45, FLCTL, I2C0, I2C1, SIM, USB, enumerator
435 INTC_GROUP(MMC, MMC_FRDY, MMC_FSTAT, MMC_TRAN, MMC_ERR),
482 { 0xa4080028, 0, 16, 4, /* IPRK */ { 0, MMC, 0, SDHI } },
/linux-3.4.99/drivers/misc/iwmc3200top/
DKconfig3 depends on MMC && EXPERIMENTAL
/linux-3.4.99/drivers/misc/cb710/
DKconfig8 You will also have to select some flash card format drivers (MMC/SD,
/linux-3.4.99/drivers/net/wireless/mwifiex/
DKconfig14 depends on MWIFIEX && MMC

123