From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Alessio Ferri" <alessio.ferri@mythread.it>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Jonas Gorski" <jonas.gorski@gmail.com>
Cc: linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v3 4/5] bcma: add host driver for the BCM6362 integrated WLAN backplane
Date: Wed, 4 Nov 2026 10:16:56 -0800 [thread overview]
Message-ID: <ab9893c9-a874-4b27-b152-02fdef49ab33@broadcom.com> (raw)
In-Reply-To: <20261104-bcm6362-wlan-v3-4-e46562b2ac12@mythread.it>
On 11/3/2026 3:31 PM, Alessio Ferri wrote:
> The BCM6362 integrates a WLAN macro on a dedicated bcma backplane.
> CFE leaves the macro clock gated and in reset, the backplane is
> a big-endian peripheral, and none of the cores has a wrapper:
> gating and reset of ChipCommon and of the 802.11 core go through
> per-core control registers in a separate WLAN control block.
>
> Add a host driver for it that:
>
> - maps the ChipCommon and WLAN control register blocks;
> - enables the clock, cycles the WLAN and WLAN UBUS resets and runs the
> macro enable sequence bcma touches the backplane;
> - provides big-endian register and block I/O ops;
> - emulates BCMA_IOCTL, BCMA_IOST, BCMA_RESET_CTL and BCMA_RESET_ST
> on top of the per-core control registers. The PHY bits of
> BCMA_IOST report what b43 needs to hear;
> - sets the big_endian and wrapperless bus flags before scanning.
>
> As for the PCI and generic SoC hosts, the driver is linked into
> bcma.ko and registered from bcma_modinit().
>
> Add a MAINTAINERS entry for the driver and its binding.
>
> The 802.11 core (rev 0x16) is handled by b43 once a SPROM is
> available; on this SoC it is not stored on the chip and has to be
> provided. In openwrt i use 6362-sprom plus fixups.
>
> Signed-off-by: Alessio Ferri <alessio.ferri@mythread.it>
Very neat, with Philip's comment addressed:
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
next prev parent reply other threads:[~2026-11-04 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 23:30 [PATCH v3 0/5] bcma: support " Alessio Ferri
2026-11-03 23:30 ` [PATCH v3 1/5] dt-bindings: bus: add Broadcom BCM6362 WLAN AXI backplane Alessio Ferri
2026-11-03 23:30 ` [PATCH v3 2/5] bcma: scan: support big-endian backplanes Alessio Ferri
2026-11-04 18:15 ` Florian Fainelli
2026-11-03 23:30 ` [PATCH v3 3/5] bcma: scan: accept wrapper-less cores on wrapper-less backplanes Alessio Ferri
2026-11-04 18:15 ` Florian Fainelli
2026-11-03 23:31 ` [PATCH v3 4/5] bcma: add host driver for the BCM6362 integrated WLAN backplane Alessio Ferri
2026-11-04 9:55 ` Philipp Zabel
2026-11-04 10:51 ` Alessio Ferri
2026-11-04 18:16 ` Florian Fainelli [this message]
2026-11-03 23:31 ` [PATCH v3 5/5] MIPS: dts: bcm6362: add the " Alessio Ferri
2026-11-04 18:14 ` Florian Fainelli
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=ab9893c9-a874-4b27-b152-02fdef49ab33@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=alessio.ferri@mythread.it \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.de \
--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
all inboxes | Powered by JetHome®