mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-27 14:43:58 +08:00
1f44a2a557
Both f_max and f_min will be informed for core layer to request valid clock rate. But current setting from 'host->bus_hz' may not represent the max/min frequency properly. Even if host can actually support high speed than bus_hz, core layer will not request clock rate over bus_hz. Basically, f_max/f_min can be set with the values according to spec. And then host will make its best effort to meet the rate. Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com> Tested-by: Alim Akhtar <alim.akhtar@samsung.com> Signed-off-by: Chris Ball <cjb@laptop.org> |
||
---|---|---|
.. | ||
atmel-hsmci.txt | ||
brcm,bcm2835-sdhci.txt | ||
davinci_mmc.txt | ||
exynos-dw-mshc.txt | ||
fsl-esdhc.txt | ||
fsl-imx-esdhc.txt | ||
fsl-imx-mmc.txt | ||
kona-sdhci.txt | ||
mmc-spi-slot.txt | ||
mmc.txt | ||
mmci.txt | ||
mxs-mmc.txt | ||
nvidia,tegra20-sdhci.txt | ||
orion-sdio.txt | ||
pxa-mmc.txt | ||
rockchip-dw-mshc.txt | ||
samsung-sdhci.txt | ||
sdhci-dove.txt | ||
sdhci-pxa.txt | ||
sdhci-sirf.txt | ||
sdhci-spear.txt | ||
synopsis-dw-mshc.txt | ||
ti-omap-hsmmc.txt | ||
tmio_mmc.txt | ||
vt8500-sdmmc.txt |