From: "Heiko Stübner" <heiko@sntech.de>
To: Soeren Moch <smoch@web.de>
Cc: Kalle Valo <kvalo@codeaurora.org>,
brcm80211-dev-list.pdl@broadcom.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
brcm80211-dev-list@cypress.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/9] brcmfmac: add support for BCM4359 SDIO chipset
Date: Mon, 16 Dec 2019 00:43:22 +0100 [thread overview]
Message-ID: <2685733.IzV8dBlDb2@diego> (raw)
In-Reply-To: <22526722-1ae8-a018-0e24-81d7ad7512dd@web.de>
Hi Soeren,
Am Sonntag, 15. Dezember 2019, 22:24:10 CET schrieb Soeren Moch:
> On 12.12.19 11:59, Soeren Moch wrote:
> > On 12.12.19 10:42, Kalle Valo wrote:
> >> Soeren Moch <smoch@web.de> writes:
> >>
> >>> Add support for the BCM4359 chipset with SDIO interface and RSDB support
> >>> to the brcmfmac wireless network driver in patches 1-7.
> >>>
> >>> Enhance devicetree of the RockPro64 arm64/rockchip board to use an
> >>> AP6359SA based wifi/bt combo module with this chipset in patches 8-9.
> >>>
> >>>
> >>> Chung-Hsien Hsu (1):
> >>> brcmfmac: set F2 blocksize and watermark for 4359
> >>>
> >>> Soeren Moch (5):
> >>> brcmfmac: fix rambase for 4359/9
> >>> brcmfmac: make errors when setting roaming parameters non-fatal
> >>> brcmfmac: add support for BCM4359 SDIO chipset
> >>> arm64: dts: rockchip: RockPro64: enable wifi module at sdio0
> >>> arm64: dts: rockchip: RockPro64: hook up bluetooth at uart0
> >>>
> >>> Wright Feng (3):
> >>> brcmfmac: reset two D11 cores if chip has two D11 cores
> >>> brcmfmac: add RSDB condition when setting interface combinations
> >>> brcmfmac: not set mbss in vif if firmware does not support MBSS
> >>>
> >>> .../boot/dts/rockchip/rk3399-rockpro64.dts | 50 +++++++++++---
> >>> .../broadcom/brcm80211/brcmfmac/bcmsdh.c | 8 ++-
> >>> .../broadcom/brcm80211/brcmfmac/cfg80211.c | 68 +++++++++++++++----
> >>> .../broadcom/brcm80211/brcmfmac/chip.c | 54 ++++++++++++++-
> >>> .../broadcom/brcm80211/brcmfmac/chip.h | 1 +
> >>> .../broadcom/brcm80211/brcmfmac/pcie.c | 2 +-
> >>> .../broadcom/brcm80211/brcmfmac/sdio.c | 17 +++++
> >>> include/linux/mmc/sdio_ids.h | 2 +
> >>> 8 files changed, 176 insertions(+), 26 deletions(-)
> >> Just to make sure we are on the same page, I will apply patches 1-7 to
> >> wireless-drivers-next and patches 8-9 go to some other tree? And there
> >> are no dependencies between the brcmfmac patches and dts patches?
> >>
> > Yes, this also is my understanding. I'm glad if you are fine with
> > patches 1-7.
> > Heiko will pick up patches 8-9 later for linux-rockchip independently.
> > And if we need another round of review for patches 8-9, I think we don't
> > need to bother linux-wireless with this.
>
> Heiko,
>
> is this OK for you when patches 1-7 are merged now in wireless-drivers,
> and then I send a v3 for patches 8-9 only for you to merge in
> linux-rockchip later? Or do you prefer a full v3 for the whole series
> with only this pending clock name update in patch 9?
Nope, merging 1-7 from this v2 and then getting a v3 with only the dts
stuff is perfectly fine :-)
Heiko
next prev parent reply other threads:[~2019-12-15 23:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 23:52 [PATCH v2 0/9] brcmfmac: add support for BCM4359 SDIO chipset Soeren Moch
2019-12-11 23:52 ` [PATCH v2 1/9] brcmfmac: reset two D11 cores if chip has two D11 cores Soeren Moch
2019-12-18 19:08 ` Kalle Valo
2019-12-11 23:52 ` [PATCH v2 2/9] brcmfmac: set F2 blocksize and watermark for 4359 Soeren Moch
2019-12-11 23:52 ` [PATCH v2 3/9] brcmfmac: fix rambase for 4359/9 Soeren Moch
2019-12-12 2:07 ` Chi-Hsien Lin
2019-12-11 23:52 ` [PATCH v2 4/9] brcmfmac: make errors when setting roaming parameters non-fatal Soeren Moch
2019-12-11 23:52 ` [PATCH v2 5/9] brcmfmac: add support for BCM4359 SDIO chipset Soeren Moch
2019-12-12 1:02 ` Soeren Moch
2019-12-12 2:09 ` Chi-Hsien Lin
2019-12-12 8:33 ` Ulf Hansson
2019-12-11 23:52 ` [PATCH v2 6/9] brcmfmac: add RSDB condition when setting interface combinations Soeren Moch
2019-12-11 23:52 ` [PATCH v2 7/9] brcmfmac: not set mbss in vif if firmware does not support MBSS Soeren Moch
2019-12-11 23:52 ` [PATCH v2 8/9] arm64: dts: rockchip: RockPro64: enable wifi module at sdio0 Soeren Moch
2019-12-11 23:52 ` [PATCH v2 9/9] arm64: dts: rockchip: RockPro64: hook up bluetooth at uart0 Soeren Moch
2019-12-12 10:22 ` Robin Murphy
2019-12-12 10:47 ` Soeren Moch
2019-12-12 9:42 ` [PATCH v2 0/9] brcmfmac: add support for BCM4359 SDIO chipset Kalle Valo
[not found] ` <0101016ef97cf6b5-2552a5e4-12de-4616-94d6-b63d9c795ed6-000000@us-west-2.amazonses.com>
2019-12-12 10:59 ` Soeren Moch
2019-12-15 21:24 ` Soeren Moch
2019-12-15 23:43 ` Heiko Stübner [this message]
2020-03-13 11:03 ` Chi-Hsien Lin
2020-03-13 13:17 ` Soeren Moch
2020-03-15 7:01 ` Chi-Hsien Lin
2019-12-18 11:55 ` Christian Hewitt
2019-12-18 23:04 ` Soeren Moch
2019-12-22 4:35 ` Christian Hewitt
2019-12-24 9:01 ` Arend Van Spriel
2019-12-24 9:44 ` Christian Hewitt
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=2685733.IzV8dBlDb2@diego \
--to=heiko@sntech.de \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=smoch@web.de \
/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;
as well as URLs for NNTP newsgroup(s).