[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53E06DB9.2040904@linux.intel.com>
Date: Tue, 05 Aug 2014 13:38:01 +0800
From: "Fu, Zhonghui" <zhonghui.fu@...ux.intel.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
CC: Arend van Spriel <arend@...adcom.com>, brudley@...adcom.com,
Franky Lin <frankyl@...adcom.com>, meuleman@...adcom.com,
linville@...driver.com, pieterpg@...adcom.com, dekim@...adcom.com,
mcgrof@...not-panic.com, antonio@...n-mesh.com,
johannes.berg@...el.com, linux-wireless@...r.kernel.org,
brcm80211-dev-list@...adcom.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org
Subject: Re: [PATCH] brcmfmac: prevent watchdog from interfering with scanning
and connecting
On 2014/8/5 0:52, Russell King - ARM Linux wrote:
> On Tue, Aug 05, 2014 at 12:36:49AM +0800, Fu, Zhonghui wrote:
>> Hi, Arend
>>
>> I investigated this issue, and its root cause is still that sdio
>> controller can't receive interrupts from WiFi chip on sdio bus when
>> sdio controller is in runtime suspend status. I am running 3.16-rc5
>> linux kernel on ASUS T100TA tablet, and using sdhci-acpi driver.
> That's the root cause. I fixed this with the Freescale i.MX SD driver
> which is now able to report pending SDIO interrupts while runtime PM
> suspended.
>
> Other host drivers probably need fixing too, or having runtime PM
> disabled on them - if you can't receive SDIO interrupts while runtime
> PM suspended, then entering runtime PM while you have a SDIO device
> attached is a bug.
>
> This is something for the MMC people to deal with rather than Arend.
>
Yes, this should be sdhci-acpi bug, I will contact MMC people for this issue.
Thanks,
Zhonghui
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists