Patch Set 7/12 [PATCH 1/2] sdhci: sdhci.[ch] support setting f_max clock via call back need ability to set f_max independent of max_clk. We cannot use the quirk SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN since the clock is not broken and on mmp2 is fixed at 200MHz. On some pxa platforms and changing this value a) does not work b) causes bad clock dividers c) mmc errors On other platforms defining SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN is the right thing to do (pxa168 and pxa910) since the clock is configured via system registers and not known via the CAPABILITY Register. [PATCH 2/2] sdhci: sdhci-pxa.c add host->ops to configure f_max sdhci-pxa.c sets f_max after sdhci_add_host was called. Rather then do this after the call, define a callback to allow f_max to be obtained from platform specific code if the callback is defined. We cannot use the quirk SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN since the clock is not broken and on mmp2 is fixed at 200MHz. On some pxa platforms and changing this value a) does not work b) causes bad clock dividers c) mmc errors On other platforms defining SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN is the right thing to do (pxa168 and pxa910) since the clock is configured via system registers and not known via the CAPABILITY Register. -- 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
