diff mbox series

[wireless-drivers-next,2/2] brcmfmac: print firmware reported general status errors

Message ID 20190221103325.28228-2-zajec5@gmail.com (mailing list archive)
State Accepted
Commit c91377495192cda096e52dc09c266b0d05f16d86
Delegated to: Kalle Valo
Headers show
Series [wireless-drivers-next,1/2] brcmfmac: fix size of the struct msgbuf_ring_status | expand

Commit Message

Rafał Miłecki Feb. 21, 2019, 10:33 a.m. UTC 
From: Rafał Miłecki <rafal@milecki.pl>

Firmware may report general errors using a special message type. Add
basic support for it by simply decoding & printing an error number.

A sample situation in which firmware reports a buf error:
CONSOLE: 027084.733 no host response IOCTL buffer available..so fail the request
will now produce a "Firmware reported general error: 9" on the host.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
 .../broadcom/brcm80211/brcmfmac/msgbuf.c      | 24 +++++++++++++++++++
 1 file changed, 24 insertions(+)

Comments

Arend van Spriel Feb. 21, 2019, 10:45 a.m. UTC | #1 
On 2/21/2019 11:33 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
> 
> Firmware may report general errors using a special message type. Add
> basic support for it by simply decoding & printing an error number.
> 
> A sample situation in which firmware reports a buf error:
> CONSOLE: 027084.733 no host response IOCTL buffer available..so fail the request
> will now produce a "Firmware reported general error: 9" on the host.

Could have meaningful message instead of a number. I can do that in 
follow up patch if you do not have the information.

Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
>   .../broadcom/brcm80211/brcmfmac/msgbuf.c      | 24 +++++++++++++++++++
>   1 file changed, 24 insertions(+)
> 
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c
> index d711dc8ed606..d3780eae7f19 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c
> @@ -134,6 +134,14 @@ struct msgbuf_completion_hdr {
>   	__le16				flow_ring_id;
>   };
>   
> +/* Data struct for the MSGBUF_TYPE_GEN_STATUS */
> +struct msgbuf_gen_status {
> +	struct msgbuf_common_hdr	msg;
> +	struct msgbuf_completion_hdr	compl_hdr;
> +	__le16				write_idx;
> +	__le32				rsvd0[3];
> +};
> +
>   /* Data struct for the MSGBUF_TYPE_RING_STATUS */
>   struct msgbuf_ring_status {
>   	struct msgbuf_common_hdr	msg;
> @@ -1194,6 +1202,18 @@ brcmf_msgbuf_process_rx_complete(struct brcmf_msgbuf *msgbuf, void *buf)
>   	brcmf_netif_rx(ifp, skb);
>   }
>   
> +static void brcmf_msgbuf_process_gen_status(struct brcmf_msgbuf *msgbuf,
> +					    void *buf)
> +{
> +	struct msgbuf_gen_status *gen_status = buf;
> +	struct brcmf_pub *drvr = msgbuf->drvr;
> +	int err;
> +
> +	err = le16_to_cpu(gen_status->compl_hdr.status);
> +	if (err)
> +		bphy_err(drvr, "Firmware reported general error: %d\n", err);
> +}
> +
>   static void brcmf_msgbuf_process_ring_status(struct brcmf_msgbuf *msgbuf,
>   					     void *buf)
>   {
> @@ -1273,6 +1293,10 @@ static void brcmf_msgbuf_process_msgtype(struct brcmf_msgbuf *msgbuf, void *buf)
>   
>   	msg = (struct msgbuf_common_hdr *)buf;
>   	switch (msg->msgtype) {
> +	case MSGBUF_TYPE_GEN_STATUS:
> +		brcmf_dbg(MSGBUF, "MSGBUF_TYPE_GEN_STATUS\n");
> +		brcmf_msgbuf_process_gen_status(msgbuf, buf);
> +		break;
>   	case MSGBUF_TYPE_RING_STATUS:
>   		brcmf_dbg(MSGBUF, "MSGBUF_TYPE_RING_STATUS\n");
>   		brcmf_msgbuf_process_ring_status(msgbuf, buf);
>
Rafał Miłecki Feb. 21, 2019, 11:13 a.m. UTC | #2 
On 2019-02-21 11:45, Arend Van Spriel wrote:
> On 2/21/2019 11:33 AM, Rafał Miłecki wrote:
>> From: Rafał Miłecki <rafal@milecki.pl>
>> 
>> Firmware may report general errors using a special message type. Add
>> basic support for it by simply decoding & printing an error number.
>> 
>> A sample situation in which firmware reports a buf error:
>> CONSOLE: 027084.733 no host response IOCTL buffer available..so fail 
>> the request
>> will now produce a "Firmware reported general error: 9" on the host.
> 
> Could have meaningful message instead of a number. I can do that in
> follow up patch if you do not have the information.

That would be nice, thanks!
diff mbox series

Patch

diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c
index d711dc8ed606..d3780eae7f19 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c
@@ -134,6 +134,14 @@  struct msgbuf_completion_hdr {
 	__le16				flow_ring_id;
 };
 
+/* Data struct for the MSGBUF_TYPE_GEN_STATUS */
+struct msgbuf_gen_status {
+	struct msgbuf_common_hdr	msg;
+	struct msgbuf_completion_hdr	compl_hdr;
+	__le16				write_idx;
+	__le32				rsvd0[3];
+};
+
 /* Data struct for the MSGBUF_TYPE_RING_STATUS */
 struct msgbuf_ring_status {
 	struct msgbuf_common_hdr	msg;
@@ -1194,6 +1202,18 @@  brcmf_msgbuf_process_rx_complete(struct brcmf_msgbuf *msgbuf, void *buf)
 	brcmf_netif_rx(ifp, skb);
 }
 
+static void brcmf_msgbuf_process_gen_status(struct brcmf_msgbuf *msgbuf,
+					    void *buf)
+{
+	struct msgbuf_gen_status *gen_status = buf;
+	struct brcmf_pub *drvr = msgbuf->drvr;
+	int err;
+
+	err = le16_to_cpu(gen_status->compl_hdr.status);
+	if (err)
+		bphy_err(drvr, "Firmware reported general error: %d\n", err);
+}
+
 static void brcmf_msgbuf_process_ring_status(struct brcmf_msgbuf *msgbuf,
 					     void *buf)
 {
@@ -1273,6 +1293,10 @@  static void brcmf_msgbuf_process_msgtype(struct brcmf_msgbuf *msgbuf, void *buf)
 
 	msg = (struct msgbuf_common_hdr *)buf;
 	switch (msg->msgtype) {
+	case MSGBUF_TYPE_GEN_STATUS:
+		brcmf_dbg(MSGBUF, "MSGBUF_TYPE_GEN_STATUS\n");
+		brcmf_msgbuf_process_gen_status(msgbuf, buf);
+		break;
 	case MSGBUF_TYPE_RING_STATUS:
 		brcmf_dbg(MSGBUF, "MSGBUF_TYPE_RING_STATUS\n");
 		brcmf_msgbuf_process_ring_status(msgbuf, buf);