[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6cad823891a9bb8aa5e9bc8712896898f9747fcd.camel@perches.com>
Date: Mon, 25 Jan 2021 01:24:15 -0800
From: Joe Perches <joe@...ches.com>
To: Michael Chan <michael.chan@...adcom.com>, davem@...emloft.net
Cc: netdev@...r.kernel.org, kuba@...nel.org, gospo@...adcom.com
Subject: Re: [PATCH net-next 07/15] bnxt_en: log firmware debug notifications
On Mon, 2021-01-25 at 02:08 -0500, Michael Chan wrote:
> From: Edwin Peer <edwin.peer@...adcom.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;
Powered by blists - more mailing lists