[U-Boot] [PATCH v3 0/4] mmc: sdhci: Add support for frequency constrained peripheral interfaces

[Stefan.Herbrechtsmeier at weidmueller.de]

Hi,

> -----Ursprüngliche Nachricht-----
> Von: Jaehoon Chung [mailto:jh80.chung at samsung.com]
> 
> On 12/02/2016 10:24 PM, stefan.herbrechtsmeier at weidmueller.de wrote:
> > From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier at weidmueller.de>
> >
> >
> > The sdhci controller assumes that the base clock frequency is fully
> > supported by the peripheral and doesn't support hardware limitations.
> > Distinguish between base clock of the host controller and maximal
> > supported peripheral clock frequency of the peripheral interface.
> > This is needed for the zynq platform to support two sdhci ports with
> > different IO routings.
> 
> I understood what your purpose is...When i checked your patch, i wonder
> one thing about dwmmc controller.
> There is also using dwmci_setup_cfg() and it is assigned to cfg-
> >f_min/max with max_clk/min_clk.
> 
> I think it also needs to take your approach, right?
The driver already use a different source clock (host->bus_hz / host->get_mmc_clk) for the calculation in its own set_ios / dwmmi_setup_bus function.

> do you have any plan for dwmmc controller?
No, because it is only a local cosmetic rename and shouldn't be affected by my changes.

Regards
  Stefan



Kommanditgesellschaft - Sitz: Detmold - Amtsgericht Lemgo HRA 2790 - 
Komplementärin: Weidmüller Interface Führungsgesellschaft mbH - 
Sitz: Detmold - Amtsgericht Lemgo HRB 3924; 
Geschäftsführer: José Carlos Álvarez Tobar, Elke Eckstein, Dr. Peter Köhler, Jörg Timmermann;
USt-ID-Nr. DE124599660