Linux brcm80211 wireless device drivers
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Marek Vasut <marex@denx.de>,
	Arend Van Spriel <arend.vanspriel@broadcom.com>,
	Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org,
	"Chung-Hsien Hsu" <stanley.hsu@cypress.com>,
	"Chung-Hsien Hsu" <chung-hsien.hsu@infineon.com>,
	"Dr. David Alan Gilbert" <linux@treblig.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Carter Chen" <carter.chen@infineon.com>,
	"Duoming Zhou" <duoming@zju.edu.cn>,
	"Erick Archer" <erick.archer@outlook.com>,
	"Kees Cook" <kees@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Mathias Krause" <minipli@grsecurity.net>,
	"Matthias Brugger" <mbrugger@suse.com>,
	"Owen Huang" <Owen.Huang@infineon.com>,
	"Ulf Hansson" <ulf.hansson@linaro.org>,
	brcm80211-dev-list.pdl@broadcom.com, brcm80211@lists.linux.dev
Subject: Re: [PATCH 1/2] wifi: brcmfmac: add support for TRX firmware download
Date: Mon, 19 Aug 2024 11:09:50 -0700	[thread overview]
Message-ID: <b04c01e5-3e60-4b0b-8984-9d6e0782f5af@gmail.com> (raw)
In-Reply-To: <c95f64f1-3ebb-41ca-a935-51c1efa1256a@denx.de>

On 8/19/24 09:17, Marek Vasut wrote:
> On 8/19/24 5:52 PM, Arend Van Spriel wrote:
> 
> Hi,
> 
>>>> Add support to download TRX firmware for PCIe and SDIO.
>>>>
>>>> Signed-off-by: Chung-Hsien Hsu <chung-hsien.hsu@infineon.com>
>>>> Signed-off-by: Marek Vasut <marex@denx.de> # Upport to current 
>>>> linux-next
>>>
>>> The commit message should answer to the question 'Why?'. What's TRX
>>> firmware and why do we need it?
>>
>> I looked over the patches, but did not sit down to comment on this.
> 
> Thanks, it is real nice that someone who is actually familiar with the 
> hardware jumped in. I only upported the patches from infineon downstream.
> 
>> The TRX firmware format allows multiple images and possibly 
>> compression. Not sure if Infineon is using all this functionality. 
>> This is probably needed for 55572 device support (patch 2/2). Turns 
>> out this device has a bootloader that the driver has to talk with and 
>> that is probably where this TRX support comes from. Not something I 
>> considered to happen for SDIO and PCIe devices. There is always a 
>> puzzle to solve ;-)
>>
>> Also noticed a random seed is provided to firmware. This already there 
>> for apple chips so it should be looked at whether that code can be 
>> shared. I will follow up.
> 
> I did notice just now there is some TRX support for USB broadcom devices ?
> 

TRX is a format that is also used for partitioning flash devices, so 
there is probably some room for making a common header:

./Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt/drivers/mtd/parsers/parser_trx.c
-- 
Florian


  reply	other threads:[~2024-08-19 18:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18 20:12 [PATCH 1/2] wifi: brcmfmac: add support for TRX firmware download Marek Vasut
2024-08-18 20:12 ` [PATCH 2/2] wifi: brcmfmac: add support for CYW55572 PCIe chipset Marek Vasut
2024-08-19  8:39   ` kernel test robot
2024-08-19  3:08 ` [PATCH 1/2] wifi: brcmfmac: add support for TRX firmware download Ping-Ke Shih
2024-08-19 11:15   ` Marek Vasut
2024-08-19 14:35 ` Kalle Valo
2024-08-19 15:52   ` Arend Van Spriel
2024-08-19 16:17     ` Marek Vasut
2024-08-19 18:09       ` Florian Fainelli [this message]
2024-08-21 16:10         ` Marek Vasut
2024-08-22  8:37 ` Kalle Valo
2024-08-22 15:15   ` Marek Vasut

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=b04c01e5-3e60-4b0b-8984-9d6e0782f5af@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=Owen.Huang@infineon.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=carter.chen@infineon.com \
    --cc=chung-hsien.hsu@infineon.com \
    --cc=duoming@zju.edu.cn \
    --cc=erick.archer@outlook.com \
    --cc=gustavoars@kernel.org \
    --cc=kees@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=marex@denx.de \
    --cc=mbrugger@suse.com \
    --cc=minipli@grsecurity.net \
    --cc=stanley.hsu@cypress.com \
    --cc=ulf.hansson@linaro.org \
    --cc=zajec5@gmail.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