On 01/10/2012 20:36, Benoît Thébaudeau wrote:
> On mxc, each SDHC instance has a dedicated clock, so gd->sdhc_clk is not
> suitable for the multi-instance use case (initialization made directly with
> fsl_esdhc_initialize()).
>
> This patch fixes this issue by adding a configuration field for the
On 09/10/2012 12:35, Benoît Thébaudeau wrote:
> Hi Stefano,
>
> On Monday, October 1, 2012 8:36:25 PM, Benoît Thébaudeau wrote:
>> On mxc, each SDHC instance has a dedicated clock, so gd->sdhc_clk is
>> not
>> suitable for the multi-instance use case (initialization made
>> directly with
>> fsl_es
Hi Stefano,
On Monday, October 1, 2012 8:36:25 PM, Benoît Thébaudeau wrote:
> On mxc, each SDHC instance has a dedicated clock, so gd->sdhc_clk is
> not
> suitable for the multi-instance use case (initialization made
> directly with
> fsl_esdhc_initialize()).
>
> This patch fixes this issue by ad
On mxc, each SDHC instance has a dedicated clock, so gd->sdhc_clk is not
suitable for the multi-instance use case (initialization made directly with
fsl_esdhc_initialize()).
This patch fixes this issue by adding a configuration field for the SDHC input
clock frequency.
Signed-off-by: Benoît Théba
4 matches
Mail list logo