ath9k: Advertise midband for AR5416 devices
This has to be done if the EEPROM supports FCC Midband capability. Signed-off-by: Senthil Balasubramanian <senthilkumar@atheros.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
parent
63a75b912b
commit
ebb90cfc32
2 changed files with 5 additions and 1 deletions
|
@ -639,6 +639,7 @@ struct ar9287_eeprom {
|
|||
} __packed;
|
||||
|
||||
enum reg_ext_bitmap {
|
||||
REG_EXT_FCC_MIDBAND = 0,
|
||||
REG_EXT_JAPAN_MIDBAND = 1,
|
||||
REG_EXT_FCC_DFS_HT40 = 2,
|
||||
REG_EXT_JAPAN_NONDFS_HT40 = 3,
|
||||
|
|
|
@ -3660,7 +3660,10 @@ void ath9k_hw_fill_cap_info(struct ath_hw *ah)
|
|||
AR_EEPROM_EEREGCAP_EN_KK_U1_EVEN;
|
||||
}
|
||||
|
||||
pCap->reg_cap |= AR_EEPROM_EEREGCAP_EN_FCC_MIDBAND;
|
||||
/* Advertise midband for AR5416 with FCC midband set in eeprom */
|
||||
if (regulatory->current_rd_ext & (1 << REG_EXT_FCC_MIDBAND) &&
|
||||
AR_SREV_5416(ah))
|
||||
pCap->reg_cap |= AR_EEPROM_EEREGCAP_EN_FCC_MIDBAND;
|
||||
|
||||
pCap->num_antcfg_5ghz =
|
||||
ah->eep_ops->get_num_ant_config(ah, ATH9K_HAL_FREQ_BAND_5GHZ);
|
||||
|
|
Loading…
Add table
Reference in a new issue