Hi Sahitya,
On 2-12-2010 19:16, Sahitya Tummala wrote:
> Hi Hein Tibosch,
>
> On Fri, 2010-09-03 at 05:34 +0800, Hein_Tibosch wrote:
>> In the latest releases of the mmc driver, the freq during initialization
>> is set to a fixed 400 Khz. This was reportedly too fast for several
>> users. As there doesn't seem to be an ideal frequency which-works-for-all,
>> Pierre suggested to let the driver try several frequencies.
>> <cut>
>> + /*
>> + * First we search for SDIO...
>> + */
>> + err = mmc_send_io_op_cond(host, 0, &ocr);
>> + if (!err) {
>> + if (mmc_attach_sdio(host, ocr)) {
>> + mmc_claim_host(host);
>> + /* try SDMEM (but not MMC) even if SDIO is broken */
>> + if (mmc_send_app_op_cond(host, 0, &ocr))
> In case of SDIO error, mmc_power_off() is getting called as part of
> mmc_detach_bus(). Shouldn't we power up the host before checking for
> SDMEM? Any comments?
>
I think you should ask Michal Miroslaw, as he wrote the patch for the
SD-combo (IO + mem)*
But yes, in case of a failure, mmc_attach_sdio() will call mmc_detach_bus()
which in turn will call mmc_power_off()
And so it should be mmc_power_up() again before trying to detect SD memory.
Hein Tibosch
* http://permalink.gmane.org/gmane.linux.kernel.mmc/2052
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
