From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Gokul Sivakumar <gokulkumar.sivakumar@infineon.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
wlan-kernel-dev-list@infineon.com
Subject: Re: [PATCH wireless-next v2] wifi: brcmfmac: remove 43752 SDIO incorrectly labelled as Cypress chip
Date: Thu, 24 Jul 2025 11:39:45 +0200 [thread overview]
Message-ID: <084b0c7e-1ef4-4522-b671-d9dab84537dd@broadcom.com> (raw)
In-Reply-To: <432d50a2995dee6c421aad6bd21acceec191990e.camel@sipsolutions.net>
On 7/24/2025 11:15 AM, Johannes Berg wrote:
> On Thu, 2025-07-24 at 14:16 +0530, Gokul Sivakumar wrote:
>> Cypress(Infineon) is not the vendor for this 43752 SDIO WLAN chip, and so
>> has not officially released any firmware binary for it. It is incorrect to
>> maintain this WLAN chip with firmware vendor ID as "CYW". So relabel the
>> chip as "WCC" as suggested by the maintainer.
>>
>> Fixes: d2587c57ffd8 ("brcmfmac: add 43752 SDIO ids and initialization")
>> Fixes: f74f1ec22dc2 ("wifi: brcmfmac: add support for Cypress firmware api")
>> Signed-off-by: Gokul Sivakumar <gokulkumar.sivakumar@infineon.com>
>> ---
>>
>> v2:
>> * Relabelled the 43752-SDIO chip from CYW to WCC instead of dropping the
>> support for this chip as suggested by Arend.
>>
>
> Maybe update the subject now?
That would be nice. Please not that the vendor ID is more about the
firmware API that should be used for the device and not so much about
maintainers.
Regards,
Arend
next prev parent reply other threads:[~2025-07-24 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 8:46 [PATCH wireless-next v2] wifi: brcmfmac: remove 43752 SDIO incorrectly labelled as Cypress chip Gokul Sivakumar
2025-07-24 9:15 ` Johannes Berg
2025-07-24 9:39 ` Arend van Spriel [this message]
2025-07-24 10:01 ` Gokul Sivakumar
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=084b0c7e-1ef4-4522-b671-d9dab84537dd@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=gokulkumar.sivakumar@infineon.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wlan-kernel-dev-list@infineon.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