From: Felix Fietkau <nbd@nbd.name>
To: Ryder Lee <ryder.lee@mediatek.com>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Roy Luo <royluo@google.com>, Sean Wang <sean.wang@mediatek.com>,
Nelson Chang <nelson.chang@mediatek.com>,
YF Luo <yf.luo@mediatek.com>, Kai Lin <kai.lin@mediatek.com>,
Rorscha Yang <rorscha.yang@mediatek.com>,
Kyle Lee <kyle.lee@mediatek.com>,
Miller Shen <miller.shen@mediatek.com>,
Haipin Liang <haipin.liang@mediatek.com>,
KL Huang <kl.huang@mediatek.com>, YH chen <yh.chen@mediatek.com>,
linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Add support for MediaTek MT7615 wireless chipsets
Date: Thu, 25 Apr 2019 12:07:05 +0200 [thread overview]
Message-ID: <98c68ec4-bedb-cf6a-9221-eb82a2497e6c@nbd.name> (raw)
In-Reply-To: <cover.1554102584.git.ryder.lee@mediatek.com>
On 2019-04-01 09:16, Ryder Lee wrote:
> This adds support for MediaTek MT7615E 4x4 802.11ac PCIe-based chipsets.
>
> The series is based on the Lorenzo's patches:
> https://patchwork.kernel.org/project/linux-wireless/list/?series=95969
>
> In the legacy tx arch, we move and store the whole skb content to the
> on-device memory when we send packets via high speed interface. (e.g. PCIe)
>
> However, MT7615 and the following generation use a new tx arch called
> “cut-through”, which only passes the physical address to the hardware,
> and the packet engine will fetch the packets before transmission.
>
> It saves on-chip memory for high throughput devices, and the token mechanism
> is used to manage the release of skb under this arch.
>
> And there might be other (existing or future) chips that use the same driver
> (e.g. mt7622/mt7663...), this is a starting point to unify MTK wireless chipsets.
>
> Detailed hardware information for this chip could be found on
> https://wikidevi.com/wiki/MediaTek_MT7615
>
> Ryder Lee (4):
> mt76: add mac80211 driver for MT7615 PCIe-based chipsets
> mt76: add unlikely() for dma_mapping_error() check
> mt76: use macro for sn and seq_ctrl conversion
> MAINTAINERS : update entry for mt76 wireless driver
Applied, thanks.
- Felix
prev parent reply other threads:[~2019-04-25 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 7:16 [PATCH v3 0/4] Add support for MediaTek MT7615 wireless chipsets Ryder Lee
2019-04-01 7:16 ` [PATCH v3 1/4] mt76: add mac80211 driver for MT7615 PCIe-based chipsets Ryder Lee
2019-04-13 13:06 ` Felix Fietkau
2019-04-01 7:16 ` [PATCH v3 2/4] mt76: add unlikely() for dma_mapping_error() check Ryder Lee
2019-04-01 7:16 ` [PATCH v3 3/4] mt76: use macro for sn and seq_ctrl conversion Ryder Lee
2019-04-01 7:16 ` [PATCH v3 4/4] MAINTAINERS : update entry for mt76 wireless driver Ryder Lee
2019-04-25 10:07 ` Felix Fietkau [this message]
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=98c68ec4-bedb-cf6a-9221-eb82a2497e6c@nbd.name \
--to=nbd@nbd.name \
--cc=haipin.liang@mediatek.com \
--cc=kai.lin@mediatek.com \
--cc=kl.huang@mediatek.com \
--cc=kyle.lee@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=miller.shen@mediatek.com \
--cc=nelson.chang@mediatek.com \
--cc=rorscha.yang@mediatek.com \
--cc=royluo@google.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=yf.luo@mediatek.com \
--cc=yh.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