MT7996e debugfs question

Hi,

trying to understand how to enable the mt7996 fwlog. being new to this platform want to confirm a few things namely that the fwlog only shows on phy0! and how to read the fwlog_data file?

here are the steps

enable the logs for the phy2

echo 1 >/sys/kernel/debug/ieee80211/phy2/mt76/fw_debug_bin
echo 1 >/sys/kernel/debug/ieee80211/phy2/mt76/fw_debug_wm
echo 1 >/sys/kernel/debug/ieee80211/phy2/mt76/fw_debug_wa

ls -ltr phy2/mt76 show

-r--------    1 root     root             0 Sep 28 11:02 xmit-queues
-r--------    1 root     root             0 Sep 28 11:02 tx_stats
-r--r--r--    1 root     root             0 Sep 28 11:02 twt_stats
-rw-------    1 root     root             0 Sep 28 11:02 sys_recovery
-r--r--r--    1 root     root             0 Sep 28 11:02 rx-queues
-rw-------    1 root     root             0 Sep 28 11:02 rf_regval
-rw-------    1 root     root             0 Sep 28 11:02 regval
-rw-------    1 root     root             0 Sep 28 11:02 regidx
-rw-------    1 root     root             0 Sep 28 11:02 napi_threaded
-rw-------    1 root     root             0 Sep 28 11:02 led_pin
-rw-------    1 root     root             0 Sep 28 11:02 led_active_low
-rw-------    1 root     root             0 Sep 28 11:02 implicit_txbf
-r--------    1 root     root             0 Sep 28 11:02 hw-queues
-r--------    1 root     root             0 Sep 28 11:02 fw_util_wa
-r--------    1 root     root             0 Sep 28 11:02 eeprom
-rw-------    1 root     root             0 Sep 28 11:14 fw_debug_wm
-rw-------    1 root     root             0 Sep 28 11:14 fw_debug_bin
-rw-------    1 root     root             0 Sep 28 11:14 fw_debug_w

however

ls -ltr phy0/mt76 shows the fwlog_data

root@bananapi4:/sys/kernel/debug/ieee80211# ls -ltr phy0/mt76
-r--------    1 root     root             0 Sep 28 11:02 xmit-queues
-r--------    1 root     root             0 Sep 28 11:02 tx_stats
-r--r--r--    1 root     root             0 Sep 28 11:02 twt_stats
-rw-------    1 root     root             0 Sep 28 11:02 sys_recovery
-r--r--r--    1 root     root             0 Sep 28 11:02 rx-queues
-rw-------    1 root     root             0 Sep 28 11:02 rf_regval
-rw-------    1 root     root             0 Sep 28 11:02 regval
-rw-------    1 root     root             0 Sep 28 11:02 regidx
-rw-------    1 root     root             0 Sep 28 11:02 napi_threaded
-rw-------    1 root     root             0 Sep 28 11:02 led_pin
-rw-------    1 root     root             0 Sep 28 11:02 led_active_low
-rw-------    1 root     root             0 Sep 28 11:02 implicit_txbf
-r--------    1 root     root             0 Sep 28 11:02 hw-queues
-r--------    1 root     root             0 Sep 28 11:02 fw_util_wa
-rw-------    1 root     root             0 Sep 28 11:02 fw_debug_wm
-rw-------    1 root     root             0 Sep 28 11:02 fw_debug_wa
-rw-------    1 root     root             0 Sep 28 11:02 fw_debug_bin
-r--------    1 root     root             0 Sep 28 11:02 eeprom
-r--------    1 root     root        467129 Sep 28 11:14 fwlog_data

I believe this is a bug but wanted to confirm on other mt76 platforms if one enables the fw log it shows a fwlog_data files for each phy that has been enabled.

how to read the fwlog_data file ? I know there's mt76_test but cant get it to work ... any process to have the outputs send to syslog ?

last question :wink: anyone knows what this means ?

kern.info kernel: [ 1135.530533] ieee80211 phy0: WA: Invalid baDirection

this message only shows if I enable the fwlogs (in this case for phy2).

@nbd any thoughts ?

thank you