From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Jacobe Zang <jacobe.zang@wesion.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <heiko@sntech.de>, <kvalo@kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <conor+dt@kernel.org>
Cc: <efectn@protonmail.com>, <dsimic@manjaro.org>, <jagan@edgeble.ai>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <arend@broadcom.com>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<megi@xff.cz>, <duoming@zju.edu.cn>, <bhelgaas@google.com>,
<minipli@grsecurity.net>, <brcm80211@lists.linux.dev>,
<brcm80211-dev-list.pdl@broadcom.com>, <nick@khadas.com>
Subject: Re: [PATCH v3 5/5] wifi: brcmfmac: Add support for AP6275P
Date: Sun, 30 Jun 2024 13:17:41 +0200 [thread overview]
Message-ID: <19068dd7008.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (raw)
In-Reply-To: <20240630073605.2164346-6-jacobe.zang@wesion.com>
[-- Attachment #1: Type: text/plain, Size: 2167 bytes --]
On June 30, 2024 9:36:40 AM Jacobe Zang <jacobe.zang@wesion.com> wrote:
> This module features BCM43752A2 chipset. The firmware requires
> randomness seeding, so enabled it.
>
> Co-developed-by: Ondrej Jirman <megi@xff.cz>
> Signed-off-by: Ondrej Jirman <megi@xff.cz>
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> Link:
> https://megous.com/git/linux/commit/?h=ap6275p-6.10&id=1a99573bc8ed412e60e1969c0b29d53a0e5782e0
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c | 5 ++++-
> .../net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h | 2 ++
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
> b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
> index e84f562fc91b8..f427d664cf3a5 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
[...]
> @@ -1721,7 +1723,7 @@ static int brcmf_pcie_download_fw_nvram(struct
> brcmf_pciedev_info *devinfo,
> memcpy_toio(devinfo->tcm + address, nvram, nvram_len);
> brcmf_fw_nvram_free(nvram);
>
> - if (devinfo->otp.valid) {
> + if (devinfo->otp.valid || devinfo->ci->chip
So the problem here is that otp validity is not unambiguous. The seed
requirement is mandated by firmware and was introduced for new WCC chips
moving forward.
I would suggest to have a need_seed flag in the driver_data of the device
table (below). It currently is used only for vendor identification.
Regards,
Arend
> == BRCM_CC_43752_CHIP_ID) {
> size_t rand_len = BRCMF_RANDOM_SEED_LENGTH;
> struct brcmf_random_seed_footer footer = {
> .length = cpu_to_le32(rand_len),
> @@ -2710,6 +2712,7 @@ static const struct pci_device_id
> brcmf_pcie_devid_table[] = {
> BRCMF_PCIE_DEVICE(BRCM_PCIE_4366_5G_DEVICE_ID, BCA),
> BRCMF_PCIE_DEVICE(BRCM_PCIE_4371_DEVICE_ID, WCC),
> BRCMF_PCIE_DEVICE(BRCM_PCIE_43596_DEVICE_ID, CYW),
> + BRCMF_PCIE_DEVICE(BRCM_PCIE_43752_DEVICE_ID, WCC),
> BRCMF_PCIE_DEVICE(BRCM_PCIE_4377_DEVICE_ID, WCC),
> BRCMF_PCIE_DEVICE(BRCM_PCIE_4378_DEVICE_ID, WCC),
> BRCMF_PCIE_DEVICE(BRCM_PCIE_4387_DEVICE_ID, WCC),
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2024-06-30 11:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 7:36 [PATCH v3 0/5] Add AP6275P wireless support Jacobe Zang
2024-06-30 7:36 ` [PATCH v3 1/5] dt-bindings: net: wireless: brcm4329-fmac: add pci14e4,449d Jacobe Zang
2024-07-02 18:56 ` Arend van Spriel
2024-06-30 7:36 ` [PATCH v3 2/5] dt-bindings: net: wireless: brcm4329-fmac: add clock description for AP6275P Wi-Fi device Jacobe Zang
2024-06-30 8:26 ` Stefan Wahren
2024-07-01 8:58 ` Krzysztof Kozlowski
2024-07-02 19:05 ` Arend van Spriel
2024-06-30 7:36 ` [PATCH v3 3/5] arm64: dts: rockchip: Add AP6275P wireless support to Khadas Edge 2 Jacobe Zang
2024-07-01 8:46 ` Krzysztof Kozlowski
2024-07-01 10:38 ` Jacobe Zang
2024-07-01 11:16 ` Krzysztof Kozlowski
2024-07-01 11:31 ` Jacobe Zang
2024-07-01 13:04 ` Krzysztof Kozlowski
2024-06-30 7:36 ` [PATCH v3 4/5] wifi: brcmfmac: Add optional lpo clock enable support Jacobe Zang
2024-06-30 8:43 ` Stefan Wahren
2024-06-30 9:09 ` Jacobe Zang
2024-06-30 9:15 ` Chen-Yu Tsai
2024-06-30 9:54 ` Stefan Wahren
2024-06-30 10:51 ` Arend Van Spriel
2024-07-01 10:57 ` Jacobe Zang
2024-06-30 11:01 ` Arend Van Spriel
2024-07-01 12:03 ` kernel test robot
2024-07-01 13:48 ` kernel test robot
2024-07-02 19:20 ` Arend van Spriel
2024-06-30 7:36 ` [PATCH v3 5/5] wifi: brcmfmac: Add support for AP6275P Jacobe Zang
2024-06-30 8:34 ` Stefan Wahren
2024-06-30 8:36 ` Ondřej Jirman
2024-06-30 8:37 ` Stefan Wahren
2024-06-30 11:17 ` Arend Van Spriel [this message]
2024-07-08 10:09 ` Jacobe Zang
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=19068dd7008.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=bhelgaas@google.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=efectn@protonmail.com \
--cc=heiko@sntech.de \
--cc=jacobe.zang@wesion.com \
--cc=jagan@edgeble.ai \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=megi@xff.cz \
--cc=minipli@grsecurity.net \
--cc=netdev@vger.kernel.org \
--cc=nick@khadas.com \
--cc=pabeni@redhat.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®