From: "Rafał Miłecki" <zajec5@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "Arend van Spriel" <arend.vanspriel@broadcom.com>,
"Franky Lin" <franky.lin@broadcom.com>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"Chi-Hsien Lin" <chi-hsien.lin@cypress.com>,
"Wright Feng" <wright.feng@cypress.com>,
"Winnie Chang" <winnie.chang@cypress.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH 0/3] brcmfmac: keep wiphy during PCIe driver lifetime
Date: Tue, 3 Sep 2019 06:29:25 +0200 [thread overview]
Message-ID: <20190903042928.18621-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
Driver's main init/attach function brcmf_attach() was handling both:
wiphy allocation and driver initialization. It meant getting a new wiphy
on every init (initial, resume, error recovery).
For supplicants/authenticators and Linux users it's move convenient to
have the same wiphy over driver's lifetime. It allows e.g. automatic
recovery after a firmware crash.
This patchset was tested on BCM4366 (PCIe) and BCM43430 (SDIO).
Right now only PCIe makes use of keeping the same wiphy. I got RPi Zero
W so I'm planning to add firmware crash recovery & keep wiphy for SDIO
in the future.
Rafał Miłecki (3):
brcmfmac: move "cfg80211_ops" pointer to another struct
brcmfmac: split brcmf_attach() and brcmf_detach() functions
brcmfmac: don't realloc wiphy during PCIe reset
.../broadcom/brcm80211/brcmfmac/bus.h | 4 +-
.../broadcom/brcm80211/brcmfmac/cfg80211.c | 1 -
.../broadcom/brcm80211/brcmfmac/cfg80211.h | 1 -
.../broadcom/brcm80211/brcmfmac/core.c | 42 ++++++++++++++-----
.../broadcom/brcm80211/brcmfmac/core.h | 1 +
.../broadcom/brcm80211/brcmfmac/pcie.c | 13 +++++-
.../broadcom/brcm80211/brcmfmac/sdio.c | 15 +++++--
.../broadcom/brcm80211/brcmfmac/usb.c | 34 ++++++++++++---
8 files changed, 87 insertions(+), 24 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-03 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 4:29 Rafał Miłecki [this message]
2019-09-03 4:29 ` [PATCH 1/3] brcmfmac: move "cfg80211_ops" pointer to another struct Rafał Miłecki
2019-09-03 18:59 ` Arend Van Spriel
2019-09-09 13:15 ` Rafał Miłecki
2019-09-13 13:42 ` Kalle Valo
2019-09-03 4:29 ` [PATCH 2/3] brcmfmac: split brcmf_attach() and brcmf_detach() functions Rafał Miłecki
2019-09-03 19:03 ` Arend Van Spriel
2019-09-03 4:29 ` [PATCH 3/3] brcmfmac: don't realloc wiphy during PCIe reset Rafał Miłecki
2019-09-03 19:04 ` Arend Van Spriel
2019-09-03 18:51 ` [PATCH 0/3] brcmfmac: keep wiphy during PCIe driver lifetime Arend Van Spriel
2019-09-09 13:06 ` Rafał Miłecki
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=20190903042928.18621-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=winnie.chang@cypress.com \
--cc=wright.feng@cypress.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 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.