On 09/15/2012 11:12 AM, Stephen Warren wrote: > On 09/15/2012 03:19 AM, Arend van Spriel wrote: >> On 09/14/2012 11:53 PM, Stephen Warren wrote: >>> On 09/13/2012 01:12 PM, Arend van Spriel wrote: >>>> From: Franky Lin <frankyl@xxxxxxxxxxxx> >>>> >>>> SDIO in-band interrupt is level sensitive according to SDIO standard. >>>> When the register interrupt handler gets called by SDIO stack it is >>>> running in non interrupt context and expected to clear the interrupt >>>> from the dongle. Therefore in-band and out-of-band interrupt need to >>>> be handled differently. >>> >>> Tested-by: Stephen Warren <swarren@xxxxxxxxxxxxx> >>> >>> For reference, I took next-20120914, applied this patch series, applied >>> a few patches from Wei Ni to set up the SDIO HW on Tegra correctly, and >>> tested. The last time I tried this without any patches to the brcmfmac, >>> this test caused some system instability issues. This time around, I >>> observed no instability. I tested WPA PSK, ping (or flood ping) plus >>> playing audio through ALSA. >>> >>> Is this series likely to make 3.7? >>> >> >> Thanks, Stephen >> >> Good to hear. I suspect we are close to the 3.7 merge window, but we do >> hope this will make it mainly for the tegra sdio issue that Wei Ni >> raised. In general the series should resolve issues when used on >> sdhci/mmc framework with in-band interrupt. >> >> Do you still need the patches from Wei Ni and are they SDIO or brcmfmac >> related? > > Some patches are needed, but they're all for Tegra-specific code to > configure the pinmux, GPIO, etc. on the Tegra SoC in order to correctly > communicate with the SDIO port, and to enable the controller. No patches > are required to the brcmfmac driver. Just to be explicit here: If this patch series (the one at the start of this email thread) makes it into 3.7, I'll apply the Tegra patches to enable brcmfmac on Tegra for 3.8, and everything will work out nicely. If this patch series doesn't make it into 3.7, but gets into 3.8 instead, I'd still like to apply the Tegra patches for 3.8 as well. However, I can't apply the Tegra patches to any branch that doesn't include this patch series, or it'll cause system instability on Tegra. To that end, if this patch series doesn't make 3.7, I'd like to request that it be applied to a separate topic branch in the wireless tree, so that it can be both merged into the wireless tree for any required future work there, /and/ merged into the Tegra tree so that I can use it as a baseline to enable wireless on Tegra. Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
