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: Larry Finger <Larry.Finger@lwfinger.net>
Subject: RE: [PATCH v2] wifi: rtlwifi: rtl_usb: Use sync register writes
Date: Thu, 11 Jan 2024 01:59:30 +0000	[thread overview]
Message-ID: <d3468d464cab444f93a347e1b612ebca@realtek.com> (raw)
In-Reply-To: <400ec3ff-2ab7-469f-b32f-43dfd62621f9@gmail.com>



> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Wednesday, January 10, 2024 9:47 PM
> To: linux-wireless@vger.kernel.org
> Cc: Ping-Ke Shih <pkshih@realtek.com>; Larry Finger <Larry.Finger@lwfinger.net>
> Subject: [PATCH v2] wifi: rtlwifi: rtl_usb: Use sync register writes
> 
> Currently rtl_usb performs register writes using the async
> usb_submit_urb() function. This appears to work fine for the RTL8192CU,
> but the RTL8192DU (soon to be supported by rtlwifi) has a problem:
> it transmits everything at the 1M rate in the 2.4 GHz band. (The 5 GHz
> band is still untested.)
> 
> With this patch, rtl_usb performs the register writes using the
> synchronous usb_control_msg() function, and the RTL8192DU works
> normally. The RTL8192CU still works.
> 
> The vendor drivers use the async writes in only one function,
> rtl8192du_trigger_gpio_0 / rtl8192cu_trigger_gpio_0, which probably
> doesn't even run in real life. They use sync writes everywhere else.
> 
> Also, remove "sync" and "async" from the names of the members of
> struct rtl_io to avoid confusion:
> 
> write{8,16,32}_async -> write{8,16,32}
>  read{8,16,32}_sync  ->  read{8,16,32}
> 
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>

Acked-by: Ping-Ke Shih <pkshih@realtek.com>

> ---
> v2:
>  - Rename the members of struct rtl_io.
> ---
>  drivers/net/wireless/realtek/rtlwifi/pci.c  |  12 +-
>  drivers/net/wireless/realtek/rtlwifi/usb.c  | 163 ++++++--------------
>  drivers/net/wireless/realtek/rtlwifi/wifi.h |  30 ++--
>  3 files changed, 66 insertions(+), 139 deletions(-)
> 

[...]

> @@ -114,18 +51,15 @@ static int _usbctrl_vendorreq_sync_read(struct usb_device *udev, u8 request,
>         } while (++vendorreq_times < MAX_USBCTRL_VENDORREQ_TIMES);
> 
>         if (status < 0 && count++ < 4)
> -               pr_err("reg 0x%x, usbctrl_vendorreq TimeOut! status:0x%x value=0x%x\n",
> -                      value, status, *(u32 *)pdata);
> -       return status;
> +               pr_err("reg 0x%x, usbctrl_vendorreq TimeOut! status:0x%x value=0x%x reqtype=0x%x\n",

nit: Since you touch this, would you like to use dev_err() instead?

> +                      value, status, *(u32 *)pdata, reqtype);
>  }
> 

[...]


  reply	other threads:[~2024-01-11  1:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 13:46 [PATCH v2] wifi: rtlwifi: rtl_usb: Use sync register writes Bitterblue Smith
2024-01-11  1:59 ` Ping-Ke Shih [this message]
2024-01-11 14:52   ` 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=d3468d464cab444f93a347e1b612ebca@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@gmail.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