From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Wright Feng <wright.feng@cypress.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: franky.lin@broadcom.com, hante.meuleman@broadcom.com,
chi-hsien.lin@cypress.com, linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH v2] brcmfmac: fix CLM load error for legacy chips when user helper is enabled
Date: Mon, 15 Jan 2018 20:54:39 +0100 [thread overview]
Message-ID: <5A5D06FF.2060909@broadcom.com> (raw)
In-Reply-To: <713a8666-8b72-9198-03a3-a3656c5cb84d@cypress.com>
On 1/15/2018 11:09 AM, Wright Feng wrote:
>
[...]
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c | 12
> ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
> b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
> index 6a59d06..aaab0e6 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
> @@ -182,12 +182,12 @@ static int brcmf_c_process_clm_blob(struct
> brcmf_if *ifp)
>
> err = request_firmware(&clm, clm_name, dev);
> if (err) {
> - if (err == -ENOENT) {
> - brcmf_dbg(INFO, "continue with CLM data currently present
> in firmware\n");
> - return 0;
> - }
> - brcmf_err("request CLM blob file failed (%d)\n", err);
> - return err;
> + if (err == -ENOENT || err == -EAGAIN)
> + brcmf_info("continue with CLM data in FW\n");
> + else
> + brcmf_err("request clm_blob failed(%d) continue with CLM
> data in FW\n",
> + err);
Don't see much value in doing it this way. Either way we need to inform
the user about the consequence of this, ie.:
brcmf_info("no clm_blob available (%d). device may have limited
channels available\n", err);
> + return 0;
> }
Regards,
Arend
next prev parent reply other threads:[~2018-01-15 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 7:44 [PATCH v2] brcmfmac: fix CLM load error for legacy chips when user helper is enabled Wright Feng
2018-01-12 10:55 ` Arend van Spriel
2018-01-12 11:16 ` Kalle Valo
2018-01-15 10:09 ` Wright Feng
2018-01-15 19:54 ` Arend van Spriel [this message]
2018-01-16 1:52 ` Wright Feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5A5D06FF.2060909@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).