linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes.Sorensen@redhat.com
To: linux-wireless@vger.kernel.org
Cc: kvalo@codeaurora.org, Larry.Finger@lwfinger.net,
	Jes Sorensen <Jes.Sorensen@redhat.com>
Subject: [PATCH 04/12] rtl8xxxu: Correct rxdesc16 definition
Date: Mon, 27 Jun 2016 12:32:02 -0400	[thread overview]
Message-ID: <1467045130-18874-5-git-send-email-Jes.Sorensen@redhat.com> (raw)
In-Reply-To: <1467045130-18874-1-git-send-email-Jes.Sorensen@redhat.com>

From: Jes Sorensen <Jes.Sorensen@redhat.com>

This corrects the definition of rxdesc16 to correctly specify pkt_cnt
for aggregated packets. This is based on the code of the vendor
rtl8723au driver, as opposed to the struct definitions they use.

Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
---
 drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h
index d0ccda8..e8158c0 100644
--- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h
+++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h
@@ -135,7 +135,8 @@ struct rtl8xxxu_rxdesc16 {
 
 	u32 seq:12;
 	u32 frag:4;
-	u32 nextpktlen:14;
+	u32 pkt_cnt:8;
+	u32 reserved:6;
 	u32 nextind:1;
 	u32 reserved0:1;
 
@@ -198,7 +199,8 @@ struct rtl8xxxu_rxdesc16 {
 
 	u32 reserved0:1;
 	u32 nextind:1;
-	u32 nextpktlen:14;
+	u32 reserved:6;
+	u32 pkt_cnt:8;
 	u32 frag:4;
 	u32 seq:12;
 
-- 
2.7.4


  parent reply	other threads:[~2016-06-27 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 16:31 [PATCH 00/12] rtl8xxxu: Add RX packet DMA aggregation Jes.Sorensen
2016-06-27 16:31 ` [PATCH 01/12] rtl8xxxu: Set all ieee80211_rx_status values in parse_rx_desc() Jes.Sorensen
2016-07-08 13:42   ` [01/12] " Kalle Valo
2016-06-27 16:32 ` [PATCH 02/12] rtl8xxxu: Move skb delivery into parse_tx_desc() handler Jes.Sorensen
2016-06-27 16:32 ` [PATCH 03/12] rtl8xxxu: Obtain ieee80211_rx_status within parse_rx_desc() Jes.Sorensen
2016-06-27 16:32 ` Jes.Sorensen [this message]
2016-06-27 16:32 ` [PATCH 05/12] rtl8xxxu: Add support for aggregated RX packets on gen1 parts Jes.Sorensen
2016-06-27 16:32 ` [PATCH 06/12] rtl8xxxu: Allocate larger RX skbs when aggregation is enabled Jes.Sorensen
2016-06-27 16:32 ` [PATCH 07/12] rtl8xxxu: Adjust RX skb size to include space for phystats Jes.Sorensen
2016-06-27 16:32 ` [PATCH 08/12] rtl8xxxu: Enable aggregation for rtl8723au Jes.Sorensen
2016-06-27 16:32 ` [PATCH 09/12] rtl8xxxu: Enable aggregation for rtl8192cu/rtl8188cu/rtl8188ru Jes.Sorensen
2016-06-27 16:32 ` [PATCH 10/12] rtl8xxxu: Make DMA aggregation optional by setting a module parameter Jes.Sorensen
2016-06-27 16:32 ` [PATCH 11/12] rtl8xxxu: gen1: Set aggregation timeout (REG_RXDMA_AGG_PG_TH + 1) as well Jes.Sorensen
2016-06-27 16:32 ` [PATCH 12/12] rtl8xxxu: gen1: Add module parameters to adjust DMA aggregation parameters Jes.Sorensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1467045130-18874-5-git-send-email-Jes.Sorensen@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).