From: Lorenzo Bianconi <lorenzo@kernel.org>
To: nbd@nbd.name
Cc: lorenzo.bianconi@redhat.com, linux-wireless@vger.kernel.org,
ryder.lee@mediatek.com, shayne.chen@mediatek.com
Subject: [PATCH 0/6] mt7915: introduce dbdc support
Date: Thu, 12 Nov 2020 10:56:55 +0100 [thread overview]
Message-ID: <cover.1605173301.git.lorenzo@kernel.org> (raw)
Similar to mt7615 devices, mt7915d chipset supports dbdc mode
where the hw exports a primary phy on 2.4GHz band and a secondary
phy on 5GHz band.
This series is based on "mt76: move hw data queues in mt76_phy"
https://patchwork.kernel.org/project/linux-wireless/list/?series=382083
Tested-by: Shayne Chen <shayne.chen@mediatek.com>
Lorenzo Bianconi (6):
mt76: move band capabilities in mt76_phy
mt76: rely on mt76_phy in mt76_init_sband_2g and mt76_init_sband_5g
mt76: move band allocation in mt76_register_phy
mt76: move hw mac_addr in mt76_phy
mt76: mt7915: introduce dbdc support
mt76: mt7915: get rid of dbdc debugfs knob
drivers/net/wireless/mediatek/mt76/eeprom.c | 12 +-
drivers/net/wireless/mediatek/mt76/mac80211.c | 106 +++--
drivers/net/wireless/mediatek/mt76/mt76.h | 11 +-
.../wireless/mediatek/mt76/mt7603/eeprom.c | 6 +-
.../net/wireless/mediatek/mt76/mt7615/dma.c | 2 +-
.../wireless/mediatek/mt76/mt7615/eeprom.c | 20 +-
.../net/wireless/mediatek/mt76/mt7615/init.c | 6 +-
.../wireless/mediatek/mt76/mt76x0/eeprom.c | 12 +-
.../net/wireless/mediatek/mt76/mt76x0/init.c | 4 +-
.../net/wireless/mediatek/mt76/mt76x0/phy.c | 4 +-
.../wireless/mediatek/mt76/mt76x02_eeprom.c | 8 +-
.../net/wireless/mediatek/mt76/mt76x02_mac.c | 16 +-
.../net/wireless/mediatek/mt76/mt76x02_util.c | 8 +-
.../wireless/mediatek/mt76/mt76x2/eeprom.c | 6 +-
.../wireless/mediatek/mt76/mt76x2/pci_init.c | 2 +-
.../wireless/mediatek/mt76/mt7915/debugfs.c | 40 +-
.../net/wireless/mediatek/mt76/mt7915/dma.c | 19 +-
.../wireless/mediatek/mt76/mt7915/eeprom.c | 51 ++-
.../wireless/mediatek/mt76/mt7915/eeprom.h | 1 +
.../net/wireless/mediatek/mt76/mt7915/init.c | 386 +++++++++---------
.../net/wireless/mediatek/mt76/mt7915/mac.c | 19 +-
.../net/wireless/mediatek/mt76/mt7915/main.c | 3 +-
.../net/wireless/mediatek/mt76/mt7915/mcu.c | 4 +-
.../wireless/mediatek/mt76/mt7915/mt7915.h | 5 +-
.../net/wireless/mediatek/mt76/mt7915/pci.c | 19 +-
.../net/wireless/mediatek/mt76/mt7915/regs.h | 13 +-
drivers/net/wireless/mediatek/mt76/testmode.c | 17 +-
27 files changed, 398 insertions(+), 402 deletions(-)
--
2.26.2
next reply other threads:[~2020-11-12 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 9:56 Lorenzo Bianconi [this message]
2020-11-12 9:56 ` [PATCH 1/6] mt76: move band capabilities in mt76_phy Lorenzo Bianconi
2020-11-12 9:56 ` [PATCH 2/6] mt76: rely on mt76_phy in mt76_init_sband_2g and mt76_init_sband_5g Lorenzo Bianconi
2020-11-12 9:56 ` [PATCH 3/6] mt76: move band allocation in mt76_register_phy Lorenzo Bianconi
2020-11-12 9:56 ` [PATCH 4/6] mt76: move hw mac_addr in mt76_phy Lorenzo Bianconi
2020-11-12 9:57 ` [PATCH 5/6] mt76: mt7915: introduce dbdc support Lorenzo Bianconi
2020-11-12 9:57 ` [PATCH 6/6] mt76: mt7915: get rid of dbdc debugfs knob Lorenzo Bianconi
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=cover.1605173301.git.lorenzo@kernel.org \
--to=lorenzo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=shayne.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).