mmc: sdhci: Distinguish between base clock and maximum peripheral frequency
authorStefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
Tue, 17 Jan 2017 14:58:48 +0000 (15:58 +0100)
committerJaehoon Chung <jh80.chung@samsung.com>
Mon, 23 Jan 2017 06:37:42 +0000 (15:37 +0900)
commit6d0e34bf4e21596563e5f5950d097a2eab4c81a8
treed1d82e018cb8b85d7f0ddb102667b676fe891237
parent0c9e85f67cd86d2d7a3424ea3ebff0e6db7a3915
mmc: sdhci: Distinguish between base clock and maximum peripheral frequency

The sdhci controller assumes that the base clock frequency is fully supported by
the peripheral and doesn't support hardware limitations. The Linux kernel
distinguishes between base clock (max_clk) of the host controller and maximum
frequency (f_max) of the card interface. Use the same differentiation and allow
the platform to constrain the peripheral interface.

Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
13 files changed:
drivers/mmc/atmel_sdhci.c
drivers/mmc/bcm2835_sdhci.c
drivers/mmc/ftsdc021_sdhci.c
drivers/mmc/kona_sdhci.c
drivers/mmc/msm_sdhci.c
drivers/mmc/mv_sdhci.c
drivers/mmc/pci_mmc.c
drivers/mmc/pic32_sdhci.c
drivers/mmc/rockchip_sdhci.c
drivers/mmc/s5p_sdhci.c
drivers/mmc/sdhci.c
drivers/mmc/zynq_sdhci.c
include/sdhci.h