Hi Arnd, On 1/10/14 1:00 PM, Arnd Bergmann wrote: > On Friday 10 January 2014, Dinh Nguyen wrote: >>>> diff --git a/arch/arm/boot/dts/socfpga.dtsi b/arch/arm/boot/dts/socfpga.dtsi >>>> index f936476..e776512 100644 >>>> --- a/arch/arm/boot/dts/socfpga.dtsi >>>> +++ b/arch/arm/boot/dts/socfpga.dtsi >>>> @@ -413,6 +413,7 @@ >>>> compatible = "altr,socfpga-gate-clk"; >>>> clocks = <&f2s_periph_ref_clk>, <&main_nand_sdmmc_clk>, >>>> <&per_nand_mmc_clk>; >>>> clk-gate = <0xa0 8>; >>>> + clk-phase = <0 135>; >>> Can clk-phase be applicable commonly for various board? >>> Isn't specific timing values? >> No, the clock-phase does not change for various board. It is a >> SoC-specific property. > I'm curious about this: If the setting is fixed per soc, why is it even > configurable, rather than hardwired to the correct setting, or set up > by the boot loader? Yes, I guess it can be hardwired, but currently it is not and the values all default to 0. The bootloader does set it up, but only when the system is booting from the SD/MMC source. When booting from other flash medium(i.e. NAND, QSPI), these SD/MMC settings are not set, so they must be set by the OS if SD/MMC is to work correctly. Dinh > > Arnd -- 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
