ath10k: properly remove padding from the start of rx payload
authorVasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Fri, 9 Sep 2016 14:25:29 +0000 (17:25 +0300)
committerKalle Valo <kvalo@qca.qualcomm.com>
Tue, 13 Sep 2016 12:31:02 +0000 (15:31 +0300)
commit9e19e13261423eeb4398177001daa874c2128aa4
treec9c88eefc019385f8473127bc92a94e95d4e6231
parentae02c8719aab19bf311b6ce2881feb844456297e
ath10k: properly remove padding from the start of rx payload

In QCA99X0 (QCA99X0, QCA9984, QCA9888 and QCA4019) family chips,
hw adds padding at the begining of the rx payload to make L3
header 4-byte aligned. In the chips doing this type of padding,
the number of bytes padded will be indicated through msdu_end:info1.
Define a hw_rx_desc_ops wrapper to retrieve the number of padded
bytes and use this while doing undecap. This should fix padding
related issues with ethernt decap format with QCA99X0, QCA9984,
QCA9888 and QCA4019 hw.

Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
[Rename operations to hw_ops for other purposes]
Signed-off-by: Benjamin Berg <benjamin@sipsolutions.net>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
drivers/net/wireless/ath/ath10k/htt_rx.c
drivers/net/wireless/ath/ath10k/hw.h