From: Lorenzo Bianconi <lorenzo@kernel.org>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 01/11] mt76: mt7915: add comments about rx descriptor parsing
Date: Fri, 19 Nov 2021 17:33:25 +0100 [thread overview]
Message-ID: <YZfR1d2I6pqEzqT8@lore-desk> (raw)
In-Reply-To: <20211118164056.2965-1-greearb@candelatech.com>
[-- Attachment #1: Type: text/plain, Size: 3748 bytes --]
> From: Ben Greear <greearb@candelatech.com>
>
> This is a tricky beast to understand, so add some notes for
> next time someone is looking at this code and trying to compare
> against documents.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
>
> txs and related patches rebased on top of 5.16
>
> .../net/wireless/mediatek/mt76/mt7915/mac.c | 23 +++++++++++++++----
> 1 file changed, 18 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/wireless/mediatek/mt76/mt7915/mac.c b/drivers/net/wireless/mediatek/mt76/mt7915/mac.c
> index 8e5b87af2efb..6fbd58ae9c88 100644
> --- a/drivers/net/wireless/mediatek/mt76/mt7915/mac.c
> +++ b/drivers/net/wireless/mediatek/mt76/mt7915/mac.c
> @@ -410,6 +410,7 @@ mt7915_mac_fill_rx(struct mt7915_dev *dev, struct sk_buff *skb)
> __le32 *rxd = (__le32 *)skb->data;
> __le32 *rxv = NULL;
> u32 mode = 0;
> + /* table "PP -> HOST / X-CPU" RX Format */
> u32 rxd0 = le32_to_cpu(rxd[0]);
> u32 rxd1 = le32_to_cpu(rxd[1]);
> u32 rxd2 = le32_to_cpu(rxd[2]);
> @@ -489,7 +490,7 @@ mt7915_mac_fill_rx(struct mt7915_dev *dev, struct sk_buff *skb)
>
> rxd += 6;
> if (rxd1 & MT_RXD1_NORMAL_GROUP_4) {
> - u32 v0 = le32_to_cpu(rxd[0]);
> + u32 v0 = le32_to_cpu(rxd[0]); /* DW6 */
> u32 v2 = le32_to_cpu(rxd[2]);
>
> fc = cpu_to_le16(FIELD_GET(MT_RXD6_FRAME_CONTROL, v0));
> @@ -502,6 +503,7 @@ mt7915_mac_fill_rx(struct mt7915_dev *dev, struct sk_buff *skb)
> }
>
> if (rxd1 & MT_RXD1_NORMAL_GROUP_1) {
> + /* DW10, assuming Group-4 enabled */
> u8 *data = (u8 *)rxd;
>
> if (status->flag & RX_FLAG_DECRYPTED) {
> @@ -533,6 +535,7 @@ mt7915_mac_fill_rx(struct mt7915_dev *dev, struct sk_buff *skb)
> }
>
> if (rxd1 & MT_RXD1_NORMAL_GROUP_2) {
> + /* DW14, assuming group-1,4 */
> status->timestamp = le32_to_cpu(rxd[0]);
> status->flag |= RX_FLAG_MACTIME_START;
>
> @@ -558,18 +561,22 @@ mt7915_mac_fill_rx(struct mt7915_dev *dev, struct sk_buff *skb)
> if (rxd1 & MT_RXD1_NORMAL_GROUP_3) {
> u32 v0, v1, v2;
>
> - rxv = rxd;
> + rxv = rxd; /* DW16 assuming group 1,2,3,4 */
> rxd += 2;
> if ((u8 *)rxd - skb->data >= skb->len)
> return -EINVAL;
>
> - v0 = le32_to_cpu(rxv[0]);
> + v0 = le32_to_cpu(rxv[0]); /* DW16, P-VEC1 31:0 */
> + /* DW17, RX_RCPI copied over P-VEC 64:32 Per RX Format doc. */
This seems not so useful for everybody.
> v1 = le32_to_cpu(rxv[1]);
> - v2 = le32_to_cpu(rxv[2]);
> + v2 = le32_to_cpu(rxv[2]); /* first DW of group-5, C-RXV */
>
> if (v0 & MT_PRXV_HT_AD_CODE)
> status->enc_flags |= RX_ENC_FLAG_LDPC;
>
> + /* TODO: When group-5 is enabled, use nss (and stbc) to
> + * calculate chains properly for this particular skb.
> + */
> status->chains = mphy->antenna_mask;
> status->chain_signal[0] = to_rssi(MT_PRXV_RCPI0, v1);
> status->chain_signal[1] = to_rssi(MT_PRXV_RCPI1, v1);
> @@ -581,12 +588,18 @@ mt7915_mac_fill_rx(struct mt7915_dev *dev, struct sk_buff *skb)
> if (!(status->chains & BIT(i)))
> continue;
>
> + /* TODO: Use db sum logic instead of max. */
This seems just a not for you :)
> status->signal = max(status->signal,
> status->chain_signal[i]);
> }
>
> - /* RXD Group 5 - C-RXV */
> + /* RXD Group 5 - C-RXV.
> + * Group 5 Not currently enabled for 7915 except in
> + * monitor mode.
> + * See MT_DMA_DCR0_RXD_G5_EN
> + */
> if (rxd1 & MT_RXD1_NORMAL_GROUP_5) {
> + /* See RXV document ... */
This is not so useful :)
> u8 stbc = FIELD_GET(MT_CRXV_HT_STBC, v2);
> u8 gi = FIELD_GET(MT_CRXV_HT_SHORT_GI, v2);
> bool cck = false;
> --
> 2.20.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-11-19 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 16:40 [PATCH 01/11] mt76: mt7915: add comments about rx descriptor parsing greearb
2021-11-18 16:40 ` [PATCH 02/11] mt76: mt7915: print out hw revision greearb
2021-11-18 16:59 ` Ryder Lee
2021-11-18 16:40 ` [PATCH 03/11] mt76: mt7915: support enabling rx group-5 status greearb
2022-01-04 10:39 ` Lorenzo Bianconi
2021-11-18 16:40 ` [PATCH 04/11] mt76: mt7915: use nss for calculating rx-chains greearb
2021-12-03 9:16 ` Felix Fietkau
2021-12-03 15:33 ` Ben Greear
2021-11-18 16:40 ` [PATCH 05/11] mt76: mt7915: ethtool group-5 rx stats information greearb
2022-01-04 10:58 ` Lorenzo Bianconi
2021-11-18 16:40 ` [PATCH 06/11] mt76: mt7915: ethtool counters for driver rx path greearb
2021-11-18 16:40 ` [PATCH 07/11] mt76: mt7915: fix rate rix and flags in txs path greearb
2022-01-04 11:15 ` Lorenzo Bianconi
2021-11-18 16:40 ` [PATCH 08/11] mt76: mt7915: add ethtool tx/rx pkts/bytes greearb
2021-11-18 16:40 ` [PATCH 09/11] mt76: mt7915: add rx-ppdu-size-out-of-range ethtool counter greearb
2021-11-18 16:40 ` [PATCH 10/11] mt76: mt7915: ethtool and mib rx stats greearb
2021-11-18 16:40 ` [PATCH 11/11] mt76: mt7915: poll mib counters every 200ms greearb
2021-11-18 17:01 ` Ryder Lee
2021-11-19 16:33 ` Lorenzo Bianconi [this message]
2021-11-19 16:41 ` [PATCH 01/11] mt76: mt7915: add comments about rx descriptor parsing Ben Greear
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=YZfR1d2I6pqEzqT8@lore-desk \
--to=lorenzo@kernel.org \
--cc=greearb@candelatech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.