| Age | Commit message (Collapse) | Author |
|---|
|
Digi 01262011 Release
|
|
Signed-off-by: Alejandro Gonzalez <alex.gonzalez@digi.com>
|
|
Note that the microSD card has no card detect capability so only the SD
card can act as a wake up source.
Signed-off-by: Alejandro Gonzalez <alex.gonzalez@digi.com>
|
|
Disable the ACMD12 error status INT when SDIO wifi
used the multi-blk transfer mode
Signed-off-by: Richard Zhu <r65037@freescale.com>
Signed-off-by: Alejandro Gonzalez <alex.gonzalez@digi.com>
|
|
SDHC3 slot in ARM2 CPU board doesn't have card detection signal.
For this case, set card state as "PRESENT" always. Please ensure
the card is inserted in ARM2 SDHC3 slot if using it.
Signed-off-by: Lily Zhang <r58066@freescale.com>
Signed-off-by: Alejandro Gonzalez <alex.gonzalez@digi.com>
|
|
1. Add MX53 eSDHC support.
2. Enable the ACMD12 on all eSDHC platforms. If using CMD12 on MX53 now,
the failure to wait for interrupt was observed.
Signed-off-by: Lily Zhang <r58066@freescale.com>
Signed-off-by: Richard Zhu <r65037@freescale.com>
Signed-off-by: Alejandro Gonzalez <alex.gonzalez@digi.com>
|
|
Atheros AR6102 wifi driver need it, or host controler will not receive sdio irq.
Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
Signed-off-by: Rob Herring <r.herring@freescale.com>
Signed-off-by: Alejandro Gonzalez <alex.gonzalez@digi.com>
|
|
This commit skips the code that disables the clock on the SDIO interface, for
the ConnectCore Wi-i.MX51. This was causing that we were losing interrupts on
the SDIO interface where the wireless module is attached.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commit adds support for the SD interface (SDIO2) connected with the
redpine wireless module. It implements a simple mechanism to pass quirks
per interface, using the platform support.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Do not disable the eSDHC clk on MX35 3DS board,
since SYSTEM can't boot up after the reset key
is pressed when the SD/MMC boot mode is used.
The root cause is that the ROM code don't ensure
the SD/MMC clk is running when boot system.
Signed-off-by: Richard Zhu <r65037@freescale.com>
|
|
The unexpected messages are printed by the kernel.
The root cause is that the I2C IO func can't be called in the
interrupt context, since the SD/MMC port and CD PIN is logically
walk through the MCU I2C bus.
Solution:Don't call the I2C IO func in the interrupt context in
card detection IRQ handler, move them to work-queue enviroment.
Signed-off-by: Richard Zhu <r65037@freescale.com>
|
|
This is i.MX BSP 5.0.0 release ported to 2.6.31
Signed-off-by: Rob Herring <r.herring@freescale.com>
Signed-off-by: Alan Tull <r80115@freescale.com>
Signed-off-by: Xinyu Chen <xinyu.chen@freescale.com>
|
