On Fri, Feb 19, 2010 at 07:55:30PM +0000, David Vrabel wrote: > Anton Vorontsov wrote: > > Some hosts (e.g. as found in CNS3xxx SOCs) report wrong value in > > CLOCK_BASE capability field, and currently there is no way to > > force the SDHCI core to use the platform-provided base clock value. > > I don't think this needs a new quirk. Change the sdhci driver to check > if the platform provides a value before reading the standard register. Well, Pierre once said that by default we should conform to the SDHCI spec, and any diviations from the spec should be handled by the quirks: http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-02/msg03385.html Spec clearly states that base clock == 0 is the case when we should fall back to the platform-provided clocks. So, for controllers that conform to the spec, following might be true: - Platform provides its own (alternate) clock, but - SDHCI block choose not to use it, and doesn't clear bits in the capability register - Then the driver should not use the platform provided clock. Thanks, -- Anton Vorontsov email: cbouatmailru@xxxxxxxxx irc://irc.freenode.net/bd2 -- 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
