public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Sascha Hauer <sha@pengutronix.de>
Subject: RE: [PATCH] wifi: rtw88: usb: Simplify rtw_usb_write_data
Date: Fri, 3 May 2024 00:35:02 +0000	[thread overview]
Message-ID: <c90907baf8554581bbdb51e65dcd943e@realtek.com> (raw)
In-Reply-To: <681e03c1-d19e-44de-bc45-e71ce14c5ed2@gmail.com>

Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> The skb created in this function always has the same headroom,
> the chip's TX descriptor size. Use chip->tx_pkt_desc_sz directly.
> 
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> ---
> This is the patch I promised earlier:
> https://lore.kernel.org/linux-wireless/cae2d330-a4fb-4570-9dde-09684af23ffd@gmail.com/
> ---
>  drivers/net/wireless/realtek/rtw88/usb.c | 14 +++++---------
>  1 file changed, 5 insertions(+), 9 deletions(-)
> 
> diff --git a/usb.c b/usb.c
> index 1dfe7c6ae4ba..ff57976b9d3b 100644
> --- a/usb.c
> +++ b/usb.c
> @@ -440,23 +440,21 @@ static int rtw_usb_write_data(struct rtw_dev *rtwdev,
>  {
>         const struct rtw_chip_info *chip = rtwdev->chip;
>         struct sk_buff *skb;
> -       unsigned int desclen, headsize, size;
> +       unsigned int size;
>         u8 qsel;
>         int ret = 0;
> 
>         size = pkt_info->tx_pkt_size;
>         qsel = pkt_info->qsel;
> -       desclen = chip->tx_pkt_desc_sz;
> -       headsize = pkt_info->offset ? pkt_info->offset : desclen;
> 
> -       skb = dev_alloc_skb(headsize + size);
> +       skb = dev_alloc_skb(chip->tx_pkt_desc_sz + size);
>         if (unlikely(!skb))
>                 return -ENOMEM;
> 
> -       skb_reserve(skb, headsize);
> +       skb_reserve(skb, chip->tx_pkt_desc_sz);
>         skb_put_data(skb, buf, size);
> -       skb_push(skb, headsize);
> -       memset(skb->data, 0, headsize);
> +       skb_push(skb, chip->tx_pkt_desc_sz);
> +       memset(skb->data, 0, chip->tx_pkt_desc_sz);
>         rtw_tx_fill_tx_desc(pkt_info, skb);
>         rtw_tx_fill_txdesc_checksum(rtwdev, pkt_info, skb->data);
> 
> @@ -471,12 +469,10 @@ static int rtw_usb_write_data(struct rtw_dev *rtwdev,
>  static int rtw_usb_write_data_rsvd_page(struct rtw_dev *rtwdev, u8 *buf,
>                                         u32 size)
>  {
> -       const struct rtw_chip_info *chip = rtwdev->chip;
>         struct rtw_tx_pkt_info pkt_info = {0};
> 
>         pkt_info.tx_pkt_size = size;
>         pkt_info.qsel = TX_DESC_QSEL_BEACON;
> -       pkt_info.offset = chip->tx_pkt_desc_sz;

pkt_info.offset is still used by rtw_tx_fill_tx_desc(), so you can't remove
this line. I think this is because Larry NAKed this patch. 



  parent reply	other threads:[~2024-05-03  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 21:23 [PATCH] wifi: rtw88: usb: Simplify rtw_usb_write_data Bitterblue Smith
2024-05-02 22:18 ` Larry Finger
2024-05-03  0:38   ` Ping-Ke Shih
2024-05-03  9:53   ` Bitterblue Smith
2024-05-03  0:35 ` Ping-Ke Shih [this message]
2024-05-03 10:13   ` Bitterblue Smith

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=c90907baf8554581bbdb51e65dcd943e@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=sha@pengutronix.de \
    /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