brcmfmac: separate firmware errors from i/o errors

Browse source

When using the firmware api it can fail simply because firmware does
not like the request or it fails due to issues in the host interface.
Currently, there is only a single error code which is confusing. So
adding a parameter to pass the firmware error separately and in case
of a firmware error always return -EBADE to user-space.

Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
Reviewed-by: Franky Lin <franky.lin@broadcom.com>
Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

...

This commit is contained in:

Arend Van Spriel 2018-01-22 21:46:40 +01:00 • committed by Kalle Valo

parent 5242a5444e

commit b69c1df472

4 changed files with 31 additions and 20 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

11

drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcdc.c

View file

16

drivers/net/wireless/broadcom/brcm80211/brcmfmac/fwil.c

View file

10

drivers/net/wireless/broadcom/brcm80211/brcmfmac/msgbuf.c

View file

14

drivers/net/wireless/broadcom/brcm80211/brcmfmac/proto.h

View file