Hi I am not sure if this is the root cause. by revert this commit.[1] our SDIO ks7010 wifi card work again in linux 3.0. check out this emails, under mailing list: SDIO single IRQ optimization breaks libertas http://permalink.gmane.org/gmane.linux.kernel.mmc/8338 [1] Revert "mmc: sdio: optimized SDIO IRQ handling for single irq" This reverts commit 06e8935febe687e2a561707d4c7ca4245d261dbe. On 11/26/2011 06:26 AM, Thomas Langås wrote:
I have a slightly weird problem; I have an Samsung Exynos 4210 with an BCM4329 wifi-chip connected through the MMC-bus using SDIO. This setup works fine with 2.6.35.7 Android-kernel, but not with 3.2-rc1 (non-Android). CMD52 read/write works correctly, but CMD53 only works with reads. All CMD53 writes fails. Here's an example output of the errorlog: [ 267.175000] brcmf_sdioh_request_word: rw=1, func=1, addr=0x0bf98, nbytes=4 [ 267.175000] mmc1: starting CMD53 arg 957f3004 flags 000001b5 [ 267.175000] mmc1: blksz 4 blocks 1 flags 00000100 tsac 1000 ms nsac 0 [ 267.175000] sdhci [sdhci_irq()]: *** mmc1 got interrupt: 0x00208003 [ 267.175000] mmc1: req done (CMD53): 0: 00001000 00000000 00000000 00000000 [ 267.175000] mmc1: 0 bytes transferred: -84 I've checked the setup registers (pad-controlls to see that all pads are set to mmc instead of gpio, and mmc registers). All are identical on Android and non-Android, so it doesn'tseem like the problem is there at least. Any ideas on how to proceed with locating the problem?
-- 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
