This is a somewhat large series and reading the message of the announcement of v3.10-rc3 I think it is good to give our story up front. Firmware-signalling is a new feature merged in for 3.10, which was a major overhaul of the transmit path in brcmfmac. During and after the merge window we still have some blanks in our test coverage and further testing revealed issues with P2P, TDLS, and power-saving clients in AP mode. These issues have been fixed in this series. As said this series is intended for 3.10 and applies to the master branch of the wireless repository. Arend van Spriel (6): brcmfmac: allow firmware-signal tlv to be longer than specified brcmfmac: remove fifo bitfield from brcmf_skbuff_cb::if_flags brcmfmac: rework credit pickup to assure consistent handling brcmfmac: explicitly indicate sk_buff is sent upon request credit brcmfmac: reducing debug logging in firmware-signalling code brcmfmac: Sent TIM information in case of data available. Hante Meuleman (10): brcmfmac: Take bus flowcontrol at credit mgmt into account. brcmfmac: On bus flow control use fw signalling or netif. brcmfmac: For FW signalling it is necessary to track gen bit. brcmfmac: Correct creditmap when credit borrowing is active. brcmfmac: Find correct MAC descriptor in case of TDLS. brcmfmac: fix invalid ifp lookup in firmware-signalling brcmfmac: Accept only first creditmap event. brcmfmac: Signalling header push and pull on logic places. brcmfmac: Fix endless loop when brcmf_fws_commit_skb fails. brcmfmac: Simplify counting transit count. drivers/net/wireless/brcm80211/brcmfmac/dhd.h | 2 + .../net/wireless/brcm80211/brcmfmac/dhd_linux.c | 21 +- drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c | 2 +- drivers/net/wireless/brcm80211/brcmfmac/fwsignal.c | 639 ++++++++++---------- drivers/net/wireless/brcm80211/brcmfmac/fwsignal.h | 1 + drivers/net/wireless/brcm80211/brcmfmac/usb.c | 8 + 6 files changed, 340 insertions(+), 333 deletions(-) -- 1.7.10.4 -- 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
