From: Kalle Valo <kvalo@kernel.org>
To: aspriel@gmail.com
Cc: arend.vanspriel@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 5/7] brcmfmac: add support Broadcom BCA firmware api
Date: Thu, 28 Jul 2022 12:38:47 +0300 [thread overview]
Message-ID: <87k07xo9ug.fsf@kernel.org> (raw)
In-Reply-To: <CAJ65rDwC3U1KSCR0G4s=11bkRAxp0b2Y8p0AFKP9BpgjQECEag@mail.gmail.com> (aspriel's message of "Mon, 13 Jun 2022 05:19:28 -0400")
aspriel@gmail.com writes:
> Broadcom BCA division develops its own firmware api and as such will
> likely diverge over time. Add support for handling this.
>
> 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>
[...]
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Kconfig
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/Kconfig
> @@ -31,6 +31,13 @@ config BRCMFMAC_VENDOR_CYW
> This option will allow the driver to communicate with devices
> shipped by Cypress.
>
> +config BRCMFMAC_VENDOR_BCA
> + bool "Broadcom BCA"
> + depends on BRCMFMAC
> + help
> + This option will allow the driver to communicate with devices
> + shipped by Broadcom BCA division.
Same comment here as in patch 3.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-07-28 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220613091915.18884-1-arend.vanspriel@broadcom.com>
2022-06-13 9:19 ` [PATCH 1/7] brcmfmac: add function to unbind device to bus layer api aspriel
2022-06-13 9:19 ` [PATCH 2/7] brcmfmac: add firmware vendor info in driver data aspriel
2022-07-28 9:31 ` Kalle Valo
2022-06-13 9:19 ` [PATCH 4/7] brcmfmac: add support for Cypress firmware api aspriel
2022-07-28 9:38 ` Kalle Valo
2022-06-13 9:19 ` [PATCH 3/7] brcmfmac: add support for vendor-specific " aspriel
2022-07-28 9:36 ` Kalle Valo
2022-07-29 9:32 ` Arend Van Spriel
2022-10-19 11:58 ` Arend Van Spriel
2022-10-24 10:49 ` Kalle Valo
2022-06-13 9:19 ` [PATCH 6/7] brcmfmac: add vendor name in revinfo debugfs file aspriel
2022-06-13 9:19 ` [PATCH 5/7] brcmfmac: add support Broadcom BCA firmware api aspriel
2022-07-28 9:38 ` Kalle Valo [this message]
2022-06-13 9:19 ` [PATCH 7/7] brcmfmac: introduce BRCMFMAC exported symbols namespace aspriel
2022-07-28 9:39 ` Kalle Valo
2022-07-29 9:38 ` Arend Van Spriel
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=87k07xo9ug.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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.