Commit 429ff56a authored by Michal Kazior's avatar Michal Kazior Committed by John W. Linville

ath10k: fix 5ghz channel definitions

Nonsense channel flags were being set.

Although it doesn't seem this was visible to the
user the patch makes sure that channel
availability won't be crippled in the future if
ath_common behaviour changes.
Signed-off-by: default avatarMichal Kazior <michal.kazior@tieto.com>
Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
parent 87b1423b
...@@ -2721,30 +2721,30 @@ static const struct ieee80211_channel ath10k_2ghz_channels[] = { ...@@ -2721,30 +2721,30 @@ static const struct ieee80211_channel ath10k_2ghz_channels[] = {
}; };
static const struct ieee80211_channel ath10k_5ghz_channels[] = { static const struct ieee80211_channel ath10k_5ghz_channels[] = {
CHAN5G(36, 5180, 14), CHAN5G(36, 5180, 0),
CHAN5G(40, 5200, 15), CHAN5G(40, 5200, 0),
CHAN5G(44, 5220, 16), CHAN5G(44, 5220, 0),
CHAN5G(48, 5240, 17), CHAN5G(48, 5240, 0),
CHAN5G(52, 5260, 18), CHAN5G(52, 5260, 0),
CHAN5G(56, 5280, 19), CHAN5G(56, 5280, 0),
CHAN5G(60, 5300, 20), CHAN5G(60, 5300, 0),
CHAN5G(64, 5320, 21), CHAN5G(64, 5320, 0),
CHAN5G(100, 5500, 22), CHAN5G(100, 5500, 0),
CHAN5G(104, 5520, 23), CHAN5G(104, 5520, 0),
CHAN5G(108, 5540, 24), CHAN5G(108, 5540, 0),
CHAN5G(112, 5560, 25), CHAN5G(112, 5560, 0),
CHAN5G(116, 5580, 26), CHAN5G(116, 5580, 0),
CHAN5G(120, 5600, 27), CHAN5G(120, 5600, 0),
CHAN5G(124, 5620, 28), CHAN5G(124, 5620, 0),
CHAN5G(128, 5640, 29), CHAN5G(128, 5640, 0),
CHAN5G(132, 5660, 30), CHAN5G(132, 5660, 0),
CHAN5G(136, 5680, 31), CHAN5G(136, 5680, 0),
CHAN5G(140, 5700, 32), CHAN5G(140, 5700, 0),
CHAN5G(149, 5745, 33), CHAN5G(149, 5745, 0),
CHAN5G(153, 5765, 34), CHAN5G(153, 5765, 0),
CHAN5G(157, 5785, 35), CHAN5G(157, 5785, 0),
CHAN5G(161, 5805, 36), CHAN5G(161, 5805, 0),
CHAN5G(165, 5825, 37), CHAN5G(165, 5825, 0),
}; };
static struct ieee80211_rate ath10k_rates[] = { static struct ieee80211_rate ath10k_rates[] = {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment