From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Mikhail Karpenko <mkarpenko@quantenna.com>,
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Subject: [PATCH 0/2] qtnfmac: add support for the new revision of qsr10g chip
Date: Thu, 21 Nov 2019 13:53:30 +0000 [thread overview]
Message-ID: <20191121135324.21715-1-sergey.matyukevich.os@quantenna.com> (raw)
Hello Kalle and all,
Here are two patches adding support for the new revision of QSR10g chip.
Major change from the driver perspective is a PCIe data path update.
Sergey Matyukevich (2):
qtnfmac: refactor data path to prepare for the next QSR10G chip revision
qtnfmac: add support for the new revision of QSR10g chip
drivers/net/wireless/quantenna/qtnfmac/bus.h | 3 +-
drivers/net/wireless/quantenna/qtnfmac/pcie/pcie.c | 4 +-
.../wireless/quantenna/qtnfmac/pcie/pearl_pcie.c | 629 ++++++++++++++++-----
.../quantenna/qtnfmac/pcie/pearl_pcie_ipc.h | 3 +
.../quantenna/qtnfmac/pcie/pearl_pcie_regs.h | 33 +-
.../net/wireless/quantenna/qtnfmac/qtn_hw_ids.h | 1 +
drivers/net/wireless/quantenna/qtnfmac/util.c | 2 +
7 files changed, 517 insertions(+), 158 deletions(-)
--
2.11.0
next reply other threads:[~2019-11-21 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 13:53 Sergey Matyukevich [this message]
2019-11-21 13:53 ` [PATCH 1/2] qtnfmac: prepare for the next chip revision Sergey Matyukevich
2019-11-21 13:53 ` [PATCH 2/2] qtnfmac: add support for the new revision of QSR10g chip Sergey Matyukevich
2019-11-21 20:15 ` Kalle Valo
2019-11-26 7:51 ` Sergey Matyukevich
2020-01-27 8:34 ` Sergey Matyukevich
2020-04-24 10:17 ` Sergey Matyukevich
2020-11-11 9:04 ` Kalle Valo
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=20191121135324.21715-1-sergey.matyukevich.os@quantenna.com \
--to=sergey.matyukevich.os@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mkarpenko@quantenna.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).