Linux wireless drivers development
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: nbd@nbd.name, ryder.lee@mediatek.com, roychl666@gmail.com,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] move skb mapping before configuring txwi
Date: Mon, 11 Mar 2019 14:17:24 +0100	[thread overview]
Message-ID: <20190311131723.GB15418@localhost.localdomain> (raw)
In-Reply-To: <cover.1552306908.git.lorenzo@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

> Move skb dma mapping before configuring txwi since new chipsets
> (e.g. mt7615) will need dma addresses to properly configure txwi.
> Introduce temporary tx_aligned4_skbs variable in order to tell mt76 layer
> if it is necessary to align the 802.11 header (it will be removed as soon
> as mac80211 will take care of it)
> 
> Lorenzo Bianconi (4):
>   mt76: move mt76x02_insert_hdr_pad in mt76-core module
>   mt76: mmio: move mt76_insert_hdr_pad in mt76_dma_tx_queue_skb
>   mt76: move skb dma mapping before running tx_prepare_skb
>   mt76: introduce mt76_tx_info data structure
> 
>  drivers/net/wireless/mediatek/mt76/dma.c      | 55 +++++++++----------
>  drivers/net/wireless/mediatek/mt76/mt76.h     | 25 ++++++++-
>  .../net/wireless/mediatek/mt76/mt7603/mac.c   |  2 +-
>  .../wireless/mediatek/mt76/mt7603/mt7603.h    |  2 +-
>  .../net/wireless/mediatek/mt76/mt76x0/pci.c   |  1 +
>  drivers/net/wireless/mediatek/mt76/mt76x02.h  |  3 +-
>  .../net/wireless/mediatek/mt76/mt76x02_txrx.c | 21 +++----
>  .../net/wireless/mediatek/mt76/mt76x02_usb.h  |  2 +-
>  .../wireless/mediatek/mt76/mt76x02_usb_core.c |  4 +-
>  .../net/wireless/mediatek/mt76/mt76x02_util.c | 16 ------
>  .../net/wireless/mediatek/mt76/mt76x2/pci.c   |  1 +
>  11 files changed, 68 insertions(+), 64 deletions(-)

I forgot to mention this series is based on:
'introduce mt76_sw_queue data structure'
https://patchwork.kernel.org/cover/10836583/

Regards,
Lorenzo

> 
> -- 
> 2.20.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2019-03-11 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 12:35 [PATCH 0/4] move skb mapping before configuring txwi Lorenzo Bianconi
2019-03-11 12:35 ` [PATCH 1/4] mt76: move mt76x02_insert_hdr_pad in mt76-core module Lorenzo Bianconi
2019-03-11 13:30   ` Stanislaw Gruszka
2019-03-11 14:02     ` Lorenzo Bianconi
2019-03-11 12:35 ` [PATCH 2/4] mt76: mmio: move mt76_insert_hdr_pad in mt76_dma_tx_queue_skb Lorenzo Bianconi
2019-03-11 13:39   ` Stanislaw Gruszka
2019-03-11 14:25     ` Lorenzo Bianconi
2019-03-11 14:58       ` Stanislaw Gruszka
2019-03-11 15:01         ` Lorenzo Bianconi
2019-03-11 12:35 ` [PATCH 3/4] mt76: move skb dma mapping before running tx_prepare_skb Lorenzo Bianconi
2019-03-11 12:35 ` [PATCH 4/4] mt76: introduce mt76_tx_info data structure Lorenzo Bianconi
2019-03-11 13:17 ` Lorenzo Bianconi [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=20190311131723.GB15418@localhost.localdomain \
    --to=lorenzo.bianconi@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=roychl666@gmail.com \
    --cc=ryder.lee@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