On 2019-04-28 23:06, Arend Van Spriel wrote:
On 4/27/2019 8:30 PM, Rafał Miłecki wrote:
From: Rafał Miłecki <[email protected]>
Normally firmware messages are printed with debugging enabled only.
It's
a good idea as firmware may print a lot of messages that normal users
don't need to care about.
However, on firmware crash, it may be very helpful to log all recent
messages. There is almost always a backtrace available as well as
rought
info on the latest actions/state.
nice... there is one minor nit below, but other than that...
Reviewed-by: Arend van Spriel <[email protected]>
Signed-off-by: Rafał Miłecki <[email protected]>
---
.../broadcom/brcm80211/brcmfmac/pcie.c | 24
++++++++++++++-----
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
index 637973fe8928..f519b050aff3 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
@@ -764,15 +764,22 @@ static void brcmf_pcie_bus_console_init(struct
brcmf_pciedev_info *devinfo)
console->base_addr, console->buf_addr, console->bufsize);
}
-
-static void brcmf_pcie_bus_console_read(struct brcmf_pciedev_info
*devinfo)
+/**
+ * brcmf_pcie_bus_console_read - reads firmware messages
+ *
+ * @error: specifies if error has occurred (prints messages
unconditionally)
+ */
+static void brcmf_pcie_bus_console_read(struct brcmf_pciedev_info
*devinfo,
+ int error)
Given how it is called I would say 'bool error' makes a bit more sense.
I even call that function passing "true" or "false" as argument. Nice
catch!
