From: Michal Kazior <michal.kazior@tieto.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: QCA9984 VHT160 support
Date: Tue, 17 May 2016 14:00:24 +0200 [thread overview]
Message-ID: <CA+BoTQkhrvS3Vz_CnDFGVdRwt=XJgrAF1oTRvyEz+96r48bjfQ@mail.gmail.com> (raw)
In-Reply-To: <572a14ee-d1b5-7b85-d292-51f583f34f17@dd-wrt.com>
On 17 May 2016 at 13:43, Sebastian Gottschall <s.gottschall@dd-wrt.com> wrote:
> Attached you will find a testing patch for VHT160 support. i tested it today
> on a QCA9984 device and it seems to work.
> feel free to make any corrections
Hi,
Send patches inline, please. Preferably via git send-email. It's a lot
easier to review them this way.
From a quick glance vht capabilities setup looks weird:
> if (ar->vht_cap_info & IEEE80211_VHT_CAP_SHORT_GI_160) {
> vht_cap.cap |= IEEE80211_VHT_CAP_SUPP_CHAN_WIDTH_160MHZ;
> vht_cap.cap |= IEEE80211_VHT_CAP_SUPP_CHAN_WIDTH_160_80PLUS80MHZ;
> }
Why? Is this really necessary?
I would expect IEEE80211_VHT_CAP_SUPP_CHAN_WIDTH_160MHZ and
IEEE80211_VHT_CAP_SUPP_CHAN_WIDTH_160_80PLUS80MHZ to be already set in
ar->vht_cap_info if the chip supports 160 or 80+80.
You also don't seem to handle 80+80 because you just as phymode to 160
regardless of center frequencies:
> !ath10k_peer_assoc_h_vht_masked(vht_mcs_mask)) {
> if (sta->bandwidth == IEEE80211_STA_RX_BW_80)
> phymode = MODE_11AC_VHT80;
> else if (sta->bandwidth == IEEE80211_STA_RX_BW_160)
> phymode = MODE_11AC_VHT160;
> else if (sta->bandwidth == IEEE80211_STA_RX_BW_40)
> phymode = MODE_11AC_VHT40;
> else if (sta->bandwidth == IEEE80211_STA_RX_BW_20)
You should probably look at sta->vht_cap and associated chanctx to
check if it isn't 80+80.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-05-17 12:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 6:11 Setting per-frame tx rate for frames injected in raw tx mode Raj Joshi
2016-05-10 16:28 ` Ben Greear
2016-05-11 6:41 ` Raj Joshi
2016-05-11 16:13 ` Ben Greear
2016-05-15 2:40 ` Raj Joshi
2016-05-15 15:17 ` Ben Greear
2016-05-15 17:15 ` Ben Greear
2016-05-17 7:14 ` Raj Joshi
2016-05-17 7:36 ` Michal Kazior
2016-05-17 7:43 ` Valo, Kalle
2016-05-17 11:43 ` QCA9984 VHT160 support Sebastian Gottschall
2016-05-17 12:00 ` Michal Kazior [this message]
[not found] ` <4e407b2c-29f9-3c74-ea94-4206632441c3@dd-wrt.com>
2016-05-17 12:18 ` Michal Kazior
2016-05-17 12:22 ` Sebastian Gottschall
2016-05-17 12:35 ` Sebastian Gottschall
2016-05-17 13:20 ` Valo, Kalle
2016-09-14 10:37 ` Valo, Kalle
2016-09-14 14:38 ` Sebastian Gottschall
2016-09-14 14:44 ` Valo, Kalle
2016-09-16 7:51 ` [PATCH] " Sebastian Gottschall
2016-09-17 6:21 ` unusual event Sebastian Gottschall
2016-10-10 16:04 ` [PATCH] QCA9984 VHT160 support Valo, Kalle
2016-10-10 16:06 ` Valo, Kalle
2016-10-11 1:30 ` Sebastian Gottschall
2016-10-14 10:06 ` Valo, Kalle
2016-10-14 10:14 ` Valo, Kalle
2016-10-18 8:20 ` Sebastian Gottschall
2016-10-18 9:16 ` Sebastian Gottschall
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='CA+BoTQkhrvS3Vz_CnDFGVdRwt=XJgrAF1oTRvyEz+96r48bjfQ@mail.gmail.com' \
--to=michal.kazior@tieto.com \
--cc=ath10k@lists.infradead.org \
--cc=s.gottschall@dd-wrt.com \
/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.