public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
* SDIO wifi card works with 2.6.36, not with 3.2
@ 2011-11-25 22:26 Thomas Langås
  2011-11-26  1:02 ` Xiangfu Liu
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Langås @ 2011-11-25 22:26 UTC (permalink / raw)
  To: linux-mmc

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?

-- 
Thomas

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: SDIO wifi card works with 2.6.36, not with 3.2
  2011-11-25 22:26 SDIO wifi card works with 2.6.36, not with 3.2 Thomas Langås
@ 2011-11-26  1:02 ` Xiangfu Liu
  2011-11-27  9:40   ` Thomas Langås
  0 siblings, 1 reply; 4+ messages in thread
From: Xiangfu Liu @ 2011-11-26  1:02 UTC (permalink / raw)
  To: Thomas Langås; +Cc: linux-mmc

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?
>



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: SDIO wifi card works with 2.6.36, not with 3.2
  2011-11-26  1:02 ` Xiangfu Liu
@ 2011-11-27  9:40   ` Thomas Langås
  2012-02-09  1:46     ` james
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Langås @ 2011-11-27  9:40 UTC (permalink / raw)
  To: linux-mmc

On Sat, Nov 26, 2011 at 2:02 AM, Xiangfu Liu <xiangfu.z@gmail.com> wrote:
> 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

Didn't help my problem, I'm afraid.  I guess I should try if the 2.6.36
non-android works and if it does do a bisect session to see if I get
anywhere with that.

-- 
Thomas

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: SDIO wifi card works with 2.6.36, not with 3.2
  2011-11-27  9:40   ` Thomas Langås
@ 2012-02-09  1:46     ` james
  0 siblings, 0 replies; 4+ messages in thread
From: james @ 2012-02-09  1:46 UTC (permalink / raw)
  To: linux-mmc

My kernel is 2.6.38.8, and WiFi is AR6103. I see exactly error message as:

[  208.327200] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000003
[  208.327226] mmc0: req done (CMD53): 0: 00001000 00000000 00000000 00000000
[  208.327227] mmc0:     4 bytes transferred: 0
[  208.327235] mmc0: starting CMD53 arg 1408a004 flags 000001b5
[  208.327238] mmc0:     blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
[  208.327260] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000003
[  208.327284] mmc0: req done (CMD53): 0: 00001000 00000000 00000000 00000000
[  208.327286] mmc0:     4 bytes transferred: 0
[  208.327295] mmc0: starting CMD53 arg 941ff804 flags 000001b5
[  208.327298] mmc0:     blksz 4 blocks 1 flags 00000100 tsac 1000 ms nsac 0
[  208.327320] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00208003
[  208.327357] mmc0: req done (CMD53): 0: 00001000 00000000 00000000 00000000
[  208.327358] mmc0:     0 bytes transferred: -84
[  208.327362] AR6000: SDIO bus operation failed! MMC stack returned : -84 
[  208.327368] Unable to send the BMI data to the device
[  208.327370] Unable to write to the device


Any help is appreciated!


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-02-09  1:50 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-11-25 22:26 SDIO wifi card works with 2.6.36, not with 3.2 Thomas Langås
2011-11-26  1:02 ` Xiangfu Liu
2011-11-27  9:40   ` Thomas Langås
2012-02-09  1:46     ` james

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox