On Thu, 2015-06-11 at 01:20 +0000, Kuninori Morimoto wrote: > Hi Ben > > Sorry for my small amount of question, but I would like to ask 1 thing > > > diff --git a/arch/arm/boot/dts/r8a7790-lager.dts > > b/arch/arm/boot/dts/r8a7790-lager.dts > > index aaa4f258e279..5f68e53c58ae 100644 > > --- a/arch/arm/boot/dts/r8a7790-lager.dts > > +++ b/arch/arm/boot/dts/r8a7790-lager.dts > > @@ -488,6 +488,9 @@ > > pinctrl-0 = <&sdhi0_pins>; > > pinctrl-names = "default"; > > > > + assigned-clocks = <&mstp3_clks R8A7790_CLK_SDHI0>; > > + assigned-clock-rates = <156000000>; > > Can we use "max-frequency" here ? > tmio/sh_mobile_sdhi have tmio_mmc_clk_update/sh_mobile_sdhi_clk_enable
The purpose of these properties is to configure the frequency of the clock supplied to the SDHI block. sh_mobile_sdhi has no code to do that but these properties are handled by the clock core. The max-frequency property tells the MMC core the maximum clock frequency that the host can run the SD bus at, but anyway tmio_mmc and sh_mobile_sdhi seem to always override it. Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
