On 13/07/18 13:55, Aapo Vienamo wrote: > This happens because sdhci_pltfm_clk_get_max_clock() does not actually > return the maximum clock rate but the current one, leading to smaller > clock rates on some platforms. I'll send a patch that fixes this for > sdhci-tegra. Although this raises the question whether the current > behaviour of sdhci_pltfm_clk_get_max_clock() is desirable or not.
Agree. There is something not right here. Cheers, Jon -- nvpublic
