Re: FW: SD card reader stopped working in kernel 3.6: CONFIG_REGULATOR troubles (solved)

2013/1/7 i...@rainer-kaluscha.de : > Thanx for the quick reply. > > The patch doesn't change anything. However, I've done some research and I'm > now pretty sure that the trouble came from the dummy regulator. > > My kernel config is based on OpenSuse's defaults which is to set > CONFIG_REGULATOR a

[PATCH 2/2] mmc: sdhci: fix dummy regulator issue

Should consider the case that dummy regulator is used for host->vmmc and host->vqmmc and skip the regulator voltage check. Signed-off-by: Kevin Liu --- drivers/mmc/host/sdhci.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/hos

[PATCH 1/2] regulator: add regulator_is_dummy function

Introduce a regulator_is_dummy function to check whether the regulator is dummy. Signed-off-by: Kevin Liu --- drivers/regulator/core.c | 17 + include/linux/regulator/consumer.h |6 ++ 2 files changed, 23 insertions(+) diff --git a/drivers/regulator/core.c b/

Re: FW: SD card read​er stopped working i​n kernel 3.6: CONFIG​_REGULATOR troubles ​(solved)​

Thanx for the quick reply. The patch doesn't change anything. However, I've done some research and I'm now pretty sure that the trouble came from the dummy regulator. My kernel config is based on OpenSuse's defaults which is to set CONFIG_REGULATOR and CONFIG_REGULATOR_DUMMY. That worked fine un

RE: [PATCH 1/2] mmc: sdhci: update timeout clock setting if SDCLK is used

Hi, Kevin My host also has this quirk(SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK), I had sent a patch use the same way as yours to calculate the max_discard_to and host->timeout_clk. But I place the code in host->ops->set_clock which in my sdhci-esdhci.h. also my host has quirk SDHCI_QUIRK_NONSTANDARD

[PATCH 1/2] mmc: sdhci: update timeout clock setting if SDCLK is used

1. If SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK is selected, getting timeout through register or callback function is useless. So skip current redundant code. 2. If SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK is selected, host uses SDCLK instead of TMCLK for data timeouts. So host->timeout_clk and mmc->max_disca

[PATCH 2/2] mmc: sdhci-pxav3: controller should use SDCLK for timeout caculation

Signed-off-by: Kevin Liu --- drivers/mmc/host/sdhci-pxav3.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mmc/host/sdhci-pxav3.c b/drivers/mmc/host/sdhci-pxav3.c index ff06aff..31dc53c 100644 --- a/drivers/mmc/host/sdhci-pxav3.c +++ b/drivers/mmc/host/sdhci-pxav3.