Re: mmc0: Timeout waiting for hardware interrupt.

Hello Christian, Sorry for the late reply. I had faced the similar problem in the past. There are certain 4.5 features like BKOPS, Sanitize, cache control operations which uses CMD6 to trigger the operation and use DAT0 line for busy signalling which was not monitored for proper completion.

[RFC V3 4/4] mmc: dw_mmc: exynos: configure SMU in exynos5420.

Exynos5420 Mobile Storage Host controller has Security Management Unit (SMU) for channel 0 and channel 1 (mainly for eMMC).This patch configures SMU for exynos5420. This patch is on top of the below patch by Doug Anderson. mmc: dw_mmc: Add exynos resume_noirq callback to clear WAKEUP_INT changes

[RFC V3 0/4] dw_mmc platform specific private data and SMU init

changes from V2: 1.dropped the bypass-smu quirk mmc: dw_mmc: exynos: configure SMU in exynos5420. 2.Changed the subject line for this patch add a quirk for SMU - configure SMU in exynos5420 mmc: dw_mmc: exynos: configure SMU in exynos5420

[RFC V3 1/4] mmc: dw_mmc: exynos: move the exynos private init

Currently platform specific private data initialisation is done by dw_mci_exynos_priv_init and dw_mci_exynos_parse_dt.As we already have separate platform specific device tree parser dw_mci_exynos_parse_dt, move the dw_mci_exynos_priv_init code to dw_mci_exynos_parse_dt. We can use the

[RFC V3 2/4] mmc: dw_mmc: socfpga: move socfpga private init

Currently platform specific private data initialisation is done by dw_mci_socfpga_priv_init and dw_mci_socfpga_parse_dt.As we already have separate platform specific device tree parser dw_mci_socfpga_parse_dt, move the dw_mci_socfpga_priv_init code to dw_mci_socfpga_parse_dt. We can use the

[RFC V3 3/4] mmc: dw_mmc: move the platform specific init call

Current platform specific private data initialisation call dw_mci_exynos_priv_init can be used to do platform specific initialisation of SMU and others in future.So the drv_data-init call has moved to dw_mci_probe. changes since V2: none changes since V1: none Signed-off-by: Yuvaraj Kumar C D

Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT)

Hi Ted, On Tue, Aug 27, 2013 at 6:01 PM, Theodore Ts'o ty...@mit.edu wrote: On Tue, Aug 27, 2013 at 05:47:22PM -0400, Kevyn-Alexandre Paré wrote: mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status

Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT)

On Wed, Aug 28, 2013 at 11:22:58AM -0400, Kevyn-Alexandre Paré wrote: We try multiple of our system ( Different micro SD from SanDisk + Overo with OMAP3) and they are all doing this with the SanDisk 64GB, 32GB :

[PATCH] mmc/dw_mmc: Add support for ARC

Adapt Kconfig to include ARC in supported architectures Signed-off-by: Mischa Jonker mjon...@synopsys.com --- drivers/mmc/host/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig index 8a4c066..6496d50 100644 ---

Re: MMC locking: mmc_request accesses from dw_mmc driver ok?

On Fri, Aug 23, 2013 at 7:06 AM, Jaehoon Chung jh80.ch...@samsung.com wrote: Hi Grant, I will check this. Hi Jaehoon! Thanks for looking into this! Do you have any comments on the problem? My impression is the mmcqd thread and DW tasklet are racing but I'm not able to pin down exactly how we

Re: [RFC V3 0/4] dw_mmc platform specific private data and SMU init

Hi Yuvaraj, I have tested on Exynos4 series. I didn't test for SMU feature. If Seungwon could test or review and confirm this patch, then looks good to me. With exynos4 series, Tested-by: Jaehoon Chung jh80.ch...@samsung.com Best Regards. Jaehoon Chung On 08/28/2013 09:08 PM, Yuvaraj Kumar C