Ping-Ke Shih <pkshih@xxxxxxxxxxx> writes: > From: Po-Hao Huang <phhuang@xxxxxxxxxxx> > > Switch port settings if AP mode does not start on port 0 because of > hardware limitation. For some ICs, beacons on ports other than zero > could misbehave and do not issue properly, to fix this we change AP > VIFs to port zero when multiple interfaces is active. > > Signed-off-by: Po-Hao Huang <phhuang@xxxxxxxxxxx> > Signed-off-by: Ping-Ke Shih <pkshih@xxxxxxxxxxx> [...] > +static void rtw_port_switch_iter(void *data, u8 *mac, struct ieee80211_vif *vif) > +{ > + struct rtw_iter_port_switch_data *iter_data = data; > + struct rtw_dev *rtwdev = iter_data->rtwdev; > + struct rtw_vif *rtwvif_target = (struct rtw_vif *)vif->drv_priv; > + struct rtw_vif *rtwvif_ap = iter_data->rtwvif_ap; > + const struct rtw_hw_reg *reg1, *reg2; > + > + if (rtwvif_target->port != RTW_PORT_0) > + return; > + > + rtw_info(rtwdev, "AP port switch from %d -> %d\n", rtwvif_ap->port, > + rtwvif_target->port); This looks more like a debug message. In normal operations (after the initialisation) the drivers should be quiet and only print messages when something unexpected happens. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches