On Mon, 2021-01-25 at 02:08 -0500, Michael Chan wrote:
> From: Edwin Peer <edwin.p...@broadcom.com>
>
> Firmware is capable of generating asynchronous debug notifications.
> The event data is opaque to the driver and is simply logged. Debug
> notifications can be enabled by turning on hardware status messages
> using the ethtool msglvl interface.
[]
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
[]
> @@ -2072,6 +2073,13 @@ static int bnxt_async_event_process(struct bnxt *bp,
> bnxt_fw_health_readl(bp, BNXT_FW_RESET_CNT_REG);
> goto async_event_process_exit;
> }
> + case ASYNC_EVENT_CMPL_EVENT_ID_DEBUG_NOTIFICATION:
> + if (netif_msg_hw(bp)) {
> + netdev_notice(bp->dev,
> + "Received firmware debug notification,
> data1: 0x%x, data2: 0x%x\n",
> + data1, data2);
> + }
netif_notice(bp, hw, bp->dev,
"Received firmware debug notification, data1:
0x%x, data2: 0x%x\n",
data1, data2);
> + goto async_event_process_exit;
> case ASYNC_EVENT_CMPL_EVENT_ID_RING_MONITOR_MSG: {
> struct bnxt_rx_ring_info *rxr;
> u16 grp_idx;
