diff options
| author |   Brian Norris <briannorris@chromium.org> | 2017-01-13 18:16:57 -0800 |
|---|---|---|
| committer |   Kalle Valo <kvalo@codeaurora.org> | 2017-01-20 11:47:23 +0200 |
| commit | 0ed917d09d517646b4dffc96427e5a4cc14056de (patch) | |
| tree | 5b47cb8bcf0f5109e4e188c435f73f7a2dac27b5 /drivers/net/wireless/marvell/mwifiex/fw.h | |
| parent | mwifiex: pcie: read FROMDEVICE DMA-able memory with READ_ONCE() (diff) | |
| download | linux-dev-0ed917d09d517646b4dffc96427e5a4cc14056de.tar.xz linux-dev-0ed917d09d517646b4dffc96427e5a4cc14056de.zip | |
mwifiex: don't complain about 'unknown event id: 0x63'
Marvell folks tell me this is a debugging event that the driver doesn't
need to handle, but on 8997 w/ firmware 16.68.1.p97, I see several of
these sorts of messages at (for instance) boot time:
[ 13.825848] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
[ 14.838561] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
[ 14.850397] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
[ 32.529923] mwifiex_pcie 0000:01:00.0: event: unknown event id: 0x63
Let's handle this "event" with a much lower verbosity.
Signed-off-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'drivers/net/wireless/marvell/mwifiex/fw.h')
| -rw-r--r-- | drivers/net/wireless/marvell/mwifiex/fw.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/wireless/marvell/mwifiex/fw.h b/drivers/net/wireless/marvell/mwifiex/fw.h index 55db158fd156..cb6a1a81d44e 100644 --- a/drivers/net/wireless/marvell/mwifiex/fw.h +++ b/drivers/net/wireless/marvell/mwifiex/fw.h @@ -550,6 +550,7 @@ enum mwifiex_channel_flags { #define EVENT_TX_DATA_PAUSE 0x00000055 #define EVENT_EXT_SCAN_REPORT 0x00000058 #define EVENT_RXBA_SYNC 0x00000059 +#define EVENT_UNKNOWN_DEBUG 0x00000063 #define EVENT_BG_SCAN_STOPPED 0x00000065 #define EVENT_REMAIN_ON_CHAN_EXPIRED 0x0000005f #define EVENT_MULTI_CHAN_INFO 0x0000006a |