
Currently the monitor mode filter settings are set for both the PMAC. Hence it is possible that the non-monitor PMAC (the PMAC on which monitor vdev is not running), can receive packets and forward them to the monitor destination ring. The above scenario will lead to a ppdu_id mismatch when reaping the monitor status ring and comparing the ppdu_id in status ring with the one in monitor destination ring, since monitor status ring will have ppdu_id from the PMAC on which monitor vdev is running, whereas monitor destination ring will have packets from both the PMAC. In order to mitigate the above issue, detect the packets in the monitor destination ring, which are not from the PMAC where monitor vdev is running, and drop them. Change-Id: I32392ceeadffd9cb7a4dd76336004a9dcbb99404 CRs-Fixed: 3318036
The below qca6290 and qca8074 folder has c files defining functions and structures to hold target specific definitions to handle differences between chips with respect to hal. Please ensure changes get applied to all platform specific files if the fixes are generic and applicable to all the folders. qca6290 hal_6290_rx.c - rx related target specific function hal_6290_srng_table.c - holds hw srng table and hal hw reg offsets array hal_6290_tx.c - tx related target specific function qca8074 hal_8074_rx.c - rx related target specific function hal_8074_srng_table.c - holds hw srng table and hal hw reg offsets array hal_8074_tx.c - tx related target specific function