On 30 July 2015 at 13:37, Stefan Agner wrote:
> Hi Ulf,
>
> What is the status on that?
>
> --
> Stefan
>
> On 2015-05-21 09:15, Stefan Agner wrote:
>> When using i.MX ESDHC driver, while entering suspend while the device
>> is in runtime PM, the sdhci_(suspend|resume)_host function are called
>>
Hi Ulf,
What is the status on that?
--
Stefan
On 2015-05-21 09:15, Stefan Agner wrote:
> When using i.MX ESDHC driver, while entering suspend while the device
> is in runtime PM, the sdhci_(suspend|resume)_host function are called
> with disabled clocks. Since this functions access the SDHC host
On 2015-05-27 12:05, Dong Aisheng wrote:
>> diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c
>> b/drivers/mmc/host/sdhci-esdhc-imx.c
>> index 82f512d..7b7b3a3 100644
>> --- a/drivers/mmc/host/sdhci-esdhc-imx.c
>> +++ b/drivers/mmc/host/sdhci-esdhc-imx.c
>> @@ -1132,7 +1132,7 @@ static int sdhci_es
On Thu, May 21, 2015 at 09:15:03AM +0200, Stefan Agner wrote:
> When using i.MX ESDHC driver, while entering suspend while the device
> is in runtime PM, the sdhci_(suspend|resume)_host function are called
> with disabled clocks. Since this functions access the SDHC host
> registers, this leads to
When using i.MX ESDHC driver, while entering suspend while the device
is in runtime PM, the sdhci_(suspend|resume)_host function are called
with disabled clocks. Since this functions access the SDHC host
registers, this leads to an external abort on Vybrid SoC:
[ 37.772967] Unhandled fault: impr
5 matches
Mail list logo