From: Kalle Valo <kvalo@kernel.org>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Hector Martin <marcan@marcan.st>,
"~postmarketos\/upstreaming\@lists.sr.ht"
<~postmarketos/upstreaming@lists.sr.ht>,
"martin.botka\@somainline.org" <martin.botka@somainline.org>,
"angelogioacchino.delregno\@somainline.org"
<angelogioacchino.delregno@somainline.org>,
"marijn.suijten\@somainline.org" <marijn.suijten@somainline.org>,
"jamipkettunen\@somainline.org" <jamipkettunen@somainline.org>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Marek Vasut <marex@denx.de>, "Zhao\,
Jiaqing" <jiaqing.zhao@intel.com>,
"Russell King \(Oracle\)" <rmk+kernel@armlinux.org.uk>,
Soon Tak Lee <soontak.lee@cypress.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl\@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"SHA-cyfmac-dev-list\@infineon.com"
<SHA-cyfmac-dev-list@infineon.com>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi
Date: Mon, 26 Sep 2022 12:27:43 +0300 [thread overview]
Message-ID: <87sfke32pc.fsf@kernel.org> (raw)
In-Reply-To: <20220922133056.eo26da4npkg6bpf2@bang-olufsen.dk> ("Alvin \=\?utf-8\?Q\?\=C5\=A0ipraga\=22's\?\= message of "Thu, 22 Sep 2022 13:30:57 +0000")
Alvin Šipraga <ALSI@bang-olufsen.dk> writes:
> On Thu, Sep 22, 2022 at 03:02:12PM +0200, Linus Walleij wrote:
>> On Thu, Sep 22, 2022 at 12:21 PM Konrad Dybcio
>> <konrad.dybcio@somainline.org> wrote:
>>
>> > Also worth noting is the 'somc' bit, meaning there are probably *some* SONY
>> > customizations, but that's also just a guess.
>>
>> What I have seen from BRCM customizations on Samsung phones is that
>> the per-device customization of firmware seems to involve the set-up of
>> some GPIO and power management pins. For example if integrated with
>> an SoC that has autonomous system resume, or if some GPIO line has
>> to be pulled to enable an external regulator or PA.
>
> At least with Infineon (formerly Cypress), as a customer you might get a
> private firmware and this will be maintained internally by them on a
> separate customer branch. Any subsequent bugfixes or feature requests
> will usually be applied to that customer branch and a new firmware built
> from it. I think their internal "mainline" branch might get merged into
> the customer branches from time to time, but this seems to be done on an
> ad-hoc basis. This is our experience at least.
>
> I would also point out that the BCM4359 is equivalent to the
> CYW88359/CYW89359 chipset, which we are using in some of our
> products. Note that this is a Cypress chipset (identifiable by the
> Version: ... (... CY) tag in the version string). But the FW Konrad is
> linking appears to be for a Broadcom chipset.
>
> FYI, here's a publicly available set of firmware files for the '4359:
>
> https://github.com/NXP/imx-firmware/tree/master/cyw-wifi-bt/1FD_CYW4359
>
> Anyway, I would second Hector's suggestion and make this a separate FW.
I also recommend having a separate firmware filename. Like Hector said,
it's easy to have a symlink in userspace if same binary can be used.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-09-26 9:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 0:16 [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi Konrad Dybcio
2022-09-21 4:37 ` Hector Martin
2022-09-21 21:26 ` Konrad Dybcio
2022-09-22 6:40 ` Hector Martin
2022-09-22 10:21 ` Konrad Dybcio
2022-09-22 13:02 ` Linus Walleij
2022-09-22 13:08 ` Hector Martin
2022-09-22 13:30 ` Alvin Šipraga
2022-09-22 20:18 ` Linus Walleij
2022-09-26 8:20 ` Stockholm syndrome with Linux wireless? Kalle Valo
2022-09-26 8:59 ` Russell King (Oracle)
2022-10-03 19:40 ` Linus Walleij
2022-10-20 14:09 ` Linus Walleij
2022-10-20 14:44 ` Dave Taht
2022-09-26 9:27 ` Kalle Valo [this message]
2022-11-18 16:47 ` [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi Konrad Dybcio
2022-11-21 13:56 ` Linus Walleij
2022-11-25 11:42 ` Konrad Dybcio
2022-11-25 11:53 ` Kalle Valo
2022-11-25 12:10 ` Konrad Dybcio
2022-11-25 12:25 ` Kalle Valo
2022-11-26 21:45 ` Linus Walleij
2022-11-28 11:17 ` Kalle Valo
2022-11-28 14:40 ` Konrad Dybcio
2022-11-29 9:19 ` Krzysztof Kozlowski
2022-12-01 11:31 ` Arend van Spriel
2022-12-02 10:33 ` Konrad Dybcio
2022-12-02 15:26 ` Arend van Spriel
2022-12-02 19:28 ` Arend Van Spriel
2022-12-06 9:58 ` Konrad Dybcio
2022-12-06 11:22 ` Arend van Spriel
2022-12-07 10:12 ` Konrad Dybcio
2022-12-06 23:37 ` Linus Walleij
2022-12-07 7:41 ` Arend Van Spriel
2022-12-07 13:42 ` Linus Walleij
2022-12-07 22:26 ` Arend van Spriel
2022-12-07 8:57 ` Konrad Dybcio
2022-12-07 11:10 ` 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=87sfke32pc.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ALSI@bang-olufsen.dk \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=jamipkettunen@somainline.org \
--cc=jiaqing.zhao@intel.com \
--cc=konrad.dybcio@somainline.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=marex@denx.de \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=soontak.lee@cypress.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.