From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
linux-wireless@vger.kernel.org
Cc: brcm80211-dev-list@broadcom.com, brcm80211-dev-list@cypress.com,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Wright Feng <wright.feng@cypress.com>,
Kalle Valo <kvalo@codeaurora.org>,
Raveendran Somu <raveendran.somu@cypress.com>
Subject: Re: [PATCH V3 6/6] brcmfmac: To support printing USB console messages
Date: Wed, 25 Mar 2020 09:46:19 +0100 [thread overview]
Message-ID: <0c2f05cf-552d-ad29-4115-f6880bc69c59@broadcom.com> (raw)
In-Reply-To: <1585124429-97371-7-git-send-email-chi-hsien.lin@cypress.com>
On 3/25/2020 9:20 AM, Chi-Hsien Lin wrote:
> From: Raveendran Somu <raveendran.somu@cypress.com>
>
> This change is to add support for printing the firmware
> console messges of a USB interface chip to the host.
> To enable this feature, build option '-msgtrace' should be
Given this description I expected a feature flag would be added in the
driver. Can we detect it on driver side?
Regards,
Arend
prev parent reply other threads:[~2020-03-25 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 8:20 [PATCH V3 0/6] brcmfmac: USB change series Chi-Hsien Lin
2020-03-25 8:20 ` [PATCH V3 1/6] brcmfmac: Fix driver crash on USB control transfer timeout Chi-Hsien Lin
2020-03-26 9:44 ` Kalle Valo
2020-03-25 8:20 ` [PATCH V3 2/6] brcmfmac: Fix double freeing in the fmac usb data path Chi-Hsien Lin
2020-03-25 8:20 ` [PATCH V3 3/6] brcmfmac: fix the incorrect return value in brcmf_inform_single_bss() Chi-Hsien Lin
2020-03-25 8:20 ` [PATCH V3 4/6] brcmfmac: increase max hanger slots from 1K to 3K in fws layer Chi-Hsien Lin
2020-03-25 8:20 ` [PATCH V3 5/6] brcmfmac: add USB autosuspend feature support Chi-Hsien Lin
2020-03-25 8:20 ` [PATCH V3 6/6] brcmfmac: To support printing USB console messages Chi-Hsien Lin
2020-03-25 8:46 ` Arend Van Spriel [this message]
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=0c2f05cf-552d-ad29-4115-f6880bc69c59@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.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=raveendran.somu@cypress.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.