ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Re: Any ideas on how to fix rssi?
Date: Wed, 14 May 2014 17:07:27 -0700	[thread overview]
Message-ID: <5374053F.40804@candelatech.com> (raw)
In-Reply-To: <5373FAA0.8090801@candelatech.com>

On 05/14/2014 04:22 PM, Ben Greear wrote:
> I'm seeing incorrect signal strength when running a rate-vs-range
> test through an attenuator.  Maybe the FIXME below is the reason?
> 
> Any suggestions on what needs doing here?

Actually, it wasn't (just?) this...the patch below makes the numbers look
good, but obviously there could be a better fix:

diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c b/drivers/net/wireless/ath/ath10k/htt_rx.c
index ccbc363..f26f296 100644
--- a/drivers/net/wireless/ath/ath10k/htt_rx.c
+++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
@@ -1218,8 +1218,13 @@ static void ath10k_htt_rx_handler(struct ath10k_htt *htt,
        mpdu_ranges = htt_rx_ind_get_mpdu_ranges(rx);

        /* Fill this once, while this is per-ppdu */
-       rx_status->signal  = ATH10K_DEFAULT_NOISE_FLOOR;
-       rx_status->signal += rx->ppdu.combined_rssi;
+       if (rx->ppdu.combined_rssi) {
+               rx_status->signal  = ATH10K_DEFAULT_NOISE_FLOOR;
+               rx_status->signal += rx->ppdu.combined_rssi;
+       }
+       else {
+               rx_status->flag |= RX_FLAG_NO_SIGNAL_VAL;
+       }

        if (rx->ppdu.info0 & HTT_RX_INDICATION_INFO0_END_VALID) {
                /* TSF available only in 32-bit */
@@ -1342,7 +1347,8 @@ static void ath10k_htt_rx_frag_handler(struct ath10k_htt *htt,
        }

        /* FIXME: implement signal strength */
-
+       rx_status->flag |= RX_FLAG_NO_SIGNAL_VAL;
+
        hdr = (struct ieee80211_hdr *)msdu_head->data;
        rxd = (void *)msdu_head->data - sizeof(*rxd);
        tkip_mic_err = !!(__le32_to_cpu(rxd->attention.flags) &



> 
> Thanks,
> Ben
> 
> 
> static void ath10k_htt_rx_frag_handler(struct ath10k_htt *htt,
> 				struct htt_rx_fragment_indication *frag)
> {
> 	struct sk_buff *msdu_head, *msdu_tail;
> 	enum htt_rx_mpdu_encrypt_type enctype;
> 	struct htt_rx_desc *rxd;
> 	enum rx_msdu_decap_format fmt;
> 	struct ieee80211_rx_status *rx_status = &htt->rx_status;
> 	struct ieee80211_hdr *hdr;
> 	int ret;
> 	bool tkip_mic_err;
> 	bool decrypt_err;
> 	u8 *fw_desc;
> 	int fw_desc_len, hdrlen, paramlen;
> 	int trim;
> 
> 	fw_desc_len = __le16_to_cpu(frag->fw_rx_desc_bytes);
> 	fw_desc = (u8 *)frag->fw_msdu_rx_desc;
> 
> 	msdu_head = NULL;
> 	msdu_tail = NULL;
> 
> 	spin_lock_bh(&htt->rx_ring.lock);
> 	ret = ath10k_htt_rx_amsdu_pop(htt, &fw_desc, &fw_desc_len,
> 				      &msdu_head, &msdu_tail);
> 	spin_unlock_bh(&htt->rx_ring.lock);
> 
> 	ath10k_dbg(ATH10K_DBG_HTT_DUMP, "htt rx frag ahead\n");
> 
> 	if (ret) {
> 		ath10k_warn("failed to pop amsdu from httr rx ring for fragmented rx %d\n",
> 			    ret);
> 		ath10k_htt_rx_free_msdu_chain(msdu_head);
> 		return;
> 	}
> 
> 	/* FIXME: implement signal strength */
> 
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-05-15  0:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 23:22 Any ideas on how to fix rssi? Ben Greear
2014-05-15  0:07 ` Ben Greear [this message]
2014-05-15  5:07   ` Janusz Dziedzic
2014-05-15 14:17     ` 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=5374053F.40804@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.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