98f3bd26de
There are bandwidth 320 MHz-1 and 320 MHz-2 channelization in EHT mode. When using ACS, user might prefer one of the channelization or both, but original ACS was unable to take such preference. Another problem is that the original ACS returns only the ideal channel but no 320 MHz channelization. The function acs_get_bw_center_chan() also could not correctly return the center frequency of bandwidth 320 MHz that is decided by ACS. For example, if ACS decide the ideal channel is channel 37 with channelization 320 MHz-2 (center frequency 6265 MHz), acs_get_bw_center_chan() returns 6105 MHz, which is 320 MHz-1. Extend the support for 320 MHz so that ACS can choose the best channel according to the user's preference. Also, after calling acs_find_ideal_chan_mode(), the best channel and bandwidth can be derived. The changes are: - bw_type ACS_BW320 is divided into ACS_BW320_1 and ACS_BW320_2 - in bandwidth 320 MHz, find the best channel and bandwidth according to user's perference (320 MHz-1, 320 Mhz-2 or both are OK) - before acs_find_ideal_chan_mode() returns, update bw320_offset in iface->conf so that the best channel's channelization is recorded. - get the best center frequency from bw320_offset Co-developed-by: Money Wang <money.wang@mediatek.com> Signed-off-by: Michael-CY Lee <michael-cy.lee@mediatek.com> |
||
---|---|---|
.. | ||
ap | ||
common | ||
crypto | ||
drivers | ||
eap_common | ||
eap_peer | ||
eap_server | ||
eapol_auth | ||
eapol_supp | ||
fst | ||
l2_packet | ||
p2p | ||
pae | ||
pasn | ||
radius | ||
rsn_supp | ||
tls | ||
utils | ||
wps | ||
build.rules | ||
lib.rules | ||
Makefile | ||
objs.mk |