mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markuss Broks <markuss.broks@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
	brcm80211-dev-list.pdl@broadcom.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless-next v2] wifi: brcmfmac: Add support for BCM4361 PCIe chipset
Date: Wed, 5 Aug 2026 16:56:56 +0300	[thread overview]
Message-ID: <15ce55e2-c4cc-4579-811f-4c13e19bc6e5@gmail.com> (raw)
In-Reply-To: <2dc55d93-544f-47ec-b349-c206f5414f22@broadcom.com>

Hi Arend,

On 8/5/26 8:46 AM, Arend van Spriel wrote:
> On 04/08/2026 16:07, Markuss Broks via B4 Relay wrote:
>> From: Markuss Broks <markuss.broks@gmail.com>
>>
>> Those are the required changes for the BCM4361 PCIe chipset support.
>
> Hi Markuss,
>
> That is a brief commit message. Maybe you can provide a bit of context 
> for this patch answering these questions: Are you using this device in 
> some project? What platform are you using (if any)? What works and 
> what does not?
I was just looking at similar device additions in brcmfmac, and noticed 
they didn't have much of a description, so I decided not to add much 
either. Should I add some general info about the BCM4361 into the commit 
message?

BCM4361 is used on the Samsung Galaxy S9 device (samsung-starlte), based 
on Exynos9810. There it's connected via PCIe link. Not sure if perhaps 
there's SDIO or USB or other variants of this chipset. Everything 
"basic" seems to work, seems to connect to both 2.4GHz and 5GHz 
networks, download speed looks good. Haven't tried station mode, but I'm 
not sure what's the proper way to set it up anyway.
>
>> Signed-off-by: Markuss Broks <markuss.broks@gmail.com>
>> ---
>> Changes in v2:
>> - EDITME: describe what is new in this series revision.
>> - EDITME: use bulletpoints and terse descriptions.
>
> This really does not look very useful. Those EDITME: are for you! As the
> actual patch did not change you can probably say:
>   - fix subject format indicating wifi subsystem and wireless-next repo.

Oh, sorry, I did not notice that b4 puts the changelog there if it's not 
in the cover letter. It's been a while since I last submitted something 
:) I will add the changelog there for v2 and v3 once I submit a v3.

>
>> - Link to v1: 
>> https://patch.msgid.link/20260803-broadcom-staging-v1-1-f6f77e55b72e@gmail.com
>> ---
>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c       | 3 +++
>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c       | 3 +++
>> drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h | 2 ++
>> 3 files changed, 8 insertions(+)
>
> [...]
>
>> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c 
>> b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
>> index 55f4d7b970f2..914ae72a7b74 100644
>> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
>> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
>> @@ -59,6 +59,7 @@ BRCMF_FW_CLM_DEF(43570, "brcmfmac43570-pcie");
>> BRCMF_FW_DEF(4358, "brcmfmac4358-pcie");
>> BRCMF_FW_DEF(4359, "brcmfmac4359-pcie");
>> BRCMF_FW_DEF(4359C, "brcmfmac4359c-pcie");
>> +BRCMF_FW_CLM_DEF(4361, "brcmfmac4361-pcie");
>
> Are you sure the CLM blob is required? Can you test without it being 
> present in /lib/firmware?
I have tried without the CLM blob, it says "no clm blob available, 
device might have limited channels available" but seems to at least 
somewhat work, I haven't noticed a difference. It's still a good idea to 
load it probably, right?
>
>> BRCMF_FW_CLM_DEF(4364B2, "brcmfmac4364b2-pcie");
>> BRCMF_FW_CLM_DEF(4364B3, "brcmfmac4364b3-pcie");
>> BRCMF_FW_DEF(4365B, "brcmfmac4365b-pcie");
>
> [...]
>
>> diff --git 
>> a/drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h 
>> b/drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h
>> index df3b67ba4db2..b800cbfdece1 100644
>> --- a/drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h
>> +++ b/drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h
>
> [...]
>
>> @@ -86,6 +87,7 @@
>> #define BRCM_PCIE_43602_2G_DEVICE_ID 0x43bb
>> #define BRCM_PCIE_43602_5G_DEVICE_ID 0x43bc
>> #define BRCM_PCIE_43602_RAW_DEVICE_ID 43602
>> +#define BRCM_PCIE_4361_DEVICE_ID 0x441f
>
> Please add:
> +#define BRCM_PCIE_4361_2G_DEVICE_ID 0x4420
> +#define BRCM_PCIE_4361_5G_DEVICE_ID 0x4421

Are those some special variants of the chipset?

>
> Regards,
> Arend
>
>> #define BRCM_PCIE_4364_DEVICE_ID 0x4464
>> #define BRCM_PCIE_4365_DEVICE_ID 0x43ca
>> #define BRCM_PCIE_4365_2G_DEVICE_ID 0x43cb 

Thanks,

- Markuss


  reply	other threads:[~2026-08-05 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 14:07 Markuss Broks via B4 Relay
2026-08-05  5:46 ` Arend van Spriel
2026-08-05 13:56   ` Markuss Broks [this message]
2026-08-05 15:16     ` Arend van Spriel
2026-08-05 15:20       ` Markuss Broks

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=15ce55e2-c4cc-4579-811f-4c13e19bc6e5@gmail.com \
    --to=markuss.broks@gmail.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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®