All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Neo Jou <neojou@gmail.com>, Hans Ulli Kroll <linux@ulli-kroll.de>,
	Yan-Hsuan Chuang <tony0620emma@gmail.com>,
	Kalle Valo <kvalo@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Johannes Berg <johannes@sipsolutions.net>,
	Alexander Hochbaum <alex@appudo.com>, Da Xue <da@libre.computer>,
	Bernie Huang <phhuang@realtek.com>,
	Viktor Petrenko <g0000ga@gmail.com>,
	neo_jou <neo_jou@realtek.com>
Subject: Re: [PATCH v3 07/11] rtw88: Add common USB chip support
Date: Mon, 28 Nov 2022 11:30:00 +0100	[thread overview]
Message-ID: <20221128103000.GC29728@pengutronix.de> (raw)
In-Reply-To: <1f7aa964766c4f65b836f7e1d716a1e3@realtek.com>

On Mon, Nov 28, 2022 at 02:00:54AM +0000, Ping-Ke Shih wrote:
> 
> 
> > -----Original Message-----
> > From: Sascha Hauer <s.hauer@pengutronix.de>
> > Sent: Tuesday, November 22, 2022 10:52 PM
> > To: linux-wireless@vger.kernel.org
> > Cc: Neo Jou <neojou@gmail.com>; Hans Ulli Kroll <linux@ulli-kroll.de>; Ping-Ke Shih <pkshih@realtek.com>;
> > Yan-Hsuan Chuang <tony0620emma@gmail.com>; Kalle Valo <kvalo@kernel.org>; netdev@vger.kernel.org;
> > linux-kernel@vger.kernel.org; Martin Blumenstingl <martin.blumenstingl@googlemail.com>;
> > kernel@pengutronix.de; Johannes Berg <johannes@sipsolutions.net>; Alexander Hochbaum <alex@appudo.com>;
> > Da Xue <da@libre.computer>; Bernie Huang <phhuang@realtek.com>; Viktor Petrenko <g0000ga@gmail.com>;
> > Sascha Hauer <s.hauer@pengutronix.de>; neo_jou <neo_jou@realtek.com>
> > Subject: [PATCH v3 07/11] rtw88: Add common USB chip support
> > 
> > Add the common bits and pieces to add USB support to the RTW88 driver.
> > This is based on https://github.com/ulli-kroll/rtw88-usb.git which
> > itself is first written by Neo Jou.
> > 
> > Signed-off-by: neo_jou <neo_jou@realtek.com>
> > Signed-off-by: Hans Ulli Kroll <linux@ulli-kroll.de>
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> > 
> > Notes:
> >     Changes since v2:
> >     - Fix buffer length for aggregated tx packets
> >     - Increase maximum transmit buffer size to 20KiB as found in downstream drivers
> >     - Change register write functions to synchronous accesses instead of just firing
> >       a URB without waiting for its completion
> >     - requeue rx URBs directly in completion handler rather than having a workqueue
> >       for it.
> > 
> >     Changes since v1:
> >     - Make checkpatch.pl clean
> >     - Drop WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL flag
> >     - Use 'ret' as variable name for return values
> >     - Sort variable declarations in reverse Xmas tree order
> >     - Change potentially endless loop to a limited loop
> >     - Change locking to be more obviously correct
> >     - drop unnecessary check for !rtwdev
> >     - make sure the refill workqueue is not restarted again after we have
> >       cancelled it
> > 
> >  drivers/net/wireless/realtek/rtw88/Kconfig  |   3 +
> >  drivers/net/wireless/realtek/rtw88/Makefile |   2 +
> >  drivers/net/wireless/realtek/rtw88/mac.c    |   3 +
> >  drivers/net/wireless/realtek/rtw88/main.c   |   4 +
> >  drivers/net/wireless/realtek/rtw88/main.h   |   4 +
> >  drivers/net/wireless/realtek/rtw88/reg.h    |   1 +
> >  drivers/net/wireless/realtek/rtw88/tx.h     |  31 +
> >  drivers/net/wireless/realtek/rtw88/usb.c    | 918 ++++++++++++++++++++
> >  drivers/net/wireless/realtek/rtw88/usb.h    | 107 +++
> >  9 files changed, 1073 insertions(+)
> >  create mode 100644 drivers/net/wireless/realtek/rtw88/usb.c
> >  create mode 100644 drivers/net/wireless/realtek/rtw88/usb.h
> > 
> > diff --git a/drivers/net/wireless/realtek/rtw88/Kconfig b/drivers/net/wireless/realtek/rtw88/Kconfig
> > index e3d7cb6c12902..1624c5db69bac 100644
> > --- a/drivers/net/wireless/realtek/rtw88/Kconfig
> > +++ b/drivers/net/wireless/realtek/rtw88/Kconfig
> > @@ -16,6 +16,9 @@ config RTW88_CORE
> >  config RTW88_PCI
> >  	tristate
> > 
> > +config RTW88_USB
> > +	tristate
> > +
> >  config RTW88_8822B
> >  	tristate
> > 
> > diff --git a/drivers/net/wireless/realtek/rtw88/Makefile b/drivers/net/wireless/realtek/rtw88/Makefile
> > index 834c66ec0af9e..9e095f8181483 100644
> > --- a/drivers/net/wireless/realtek/rtw88/Makefile
> > +++ b/drivers/net/wireless/realtek/rtw88/Makefile
> > @@ -45,4 +45,6 @@ obj-$(CONFIG_RTW88_8821CE)	+= rtw88_8821ce.o
> >  rtw88_8821ce-objs		:= rtw8821ce.o
> > 
> >  obj-$(CONFIG_RTW88_PCI)		+= rtw88_pci.o
> > +obj-$(CONFIG_RTW88_USB)		+= rtw88_usb.o
> >  rtw88_pci-objs			:= pci.o
> > +rtw88_usb-objs			:= usb.o
> 
> nit: I prefer not interleaving with PCI.

Ok.

> > +static u32 rtw_usb_read(struct rtw_dev *rtwdev, u32 addr, u16 len)
> > +{
> > +	struct rtw_usb *rtwusb = rtw_get_usb_priv(rtwdev);
> > +	struct usb_device *udev = rtwusb->udev;
> > +	__le32 *data;
> > +	unsigned long flags;
> > +	int ret;
> > +	static int count;
> > +
> > +	spin_lock_irqsave(&rtwusb->usb_lock, flags);
> > +
> > +	rtwusb->usb_data_index++;
> > +	rtwusb->usb_data_index &= (RTW_USB_MAX_RXTX_COUNT - 1);
> > +
> > +	spin_unlock_irqrestore(&rtwusb->usb_lock, flags);
> > +
> > +	data = &rtwusb->usb_data[rtwusb->usb_data_index];
> 
> Don't you need to hold &rtwusb->usb_lock to access rtwusb->usb_data_index?
> rtw_usb_write() has similar code.

Right. Will rewrite to:

	spin_lock_irqsave(&rtwusb->usb_lock, flags);

	idx = rtwusb->usb_data_index;
	rtwusb->usb_data_index = (idx + 1) & (RTW_USB_MAX_RXTX_COUNT - 1);

	spin_unlock_irqrestore(&rtwusb->usb_lock, flags);

	data = &rtwusb->usb_data[idx];

> > +static void rtw_usb_write_port_tx_complete(struct urb *urb)
> > +{
> > +	struct rtw_usb_txcb *txcb = urb->context;
> > +	struct rtw_dev *rtwdev = txcb->rtwdev;
> > +	struct ieee80211_hw *hw = rtwdev->hw;
> > +
> > +	while (true) {
> 
> Is it possible to have a hard limit to prevent unexpected infinite loop?

Yes, that would be possible, but do you think it's necessary?

Each *txcb is used only once, It's allocated in rtw_usb_tx_agg_skb() and
&txcb->tx_ack_queue is filled with a limited number of skbs there. These
skbs is then iterated over in rtw_usb_write_port_tx_complete(), so I don't
see a way how we could end up in an infinite loop here.

It's not that &txcb->tx_ack_queue is filled in a concurrent thread while we
try to catch up in rtw_usb_write_port_tx_complete().

> > +	skb_head = dev_alloc_skb(RTW_USB_MAX_XMITBUF_SZ);
> > +	if (!skb_head) {
> > +		skb_head = skb_iter;
> > +		goto queue;
> > +	}
> > +
> > +	data_ptr = skb_head->data;
> > +
> > +	while (skb_iter) {
> > +		unsigned long flags;
> > +
> > +		memcpy(data_ptr, skb_iter->data, skb_iter->len);
> > +		skb_put(skb_head, skb_iter->len + align_next);
> 
> skb_put(skb_head, align_next);
> skb_put_data(skb_head, skb_iter->data, skb_iter->len);
> 
> Then, don't need to maintain 'data_ptr'.

Right. Looks much better this way.

> > +	error = usb_submit_urb(rxcb->rx_urb, GFP_ATOMIC);
> > +	if (error) {
> > +		kfree_skb(rxcb->rx_skb);
> > +		if (error != -ENODEV)
> > +			rtw_err(rtwdev, "Err sending rx data urb %d\n",
> > +				error);
> 
> nit: straighten rtw_err()

Ok.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2022-11-28 10:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 14:52 [PATCH v3 00/11] RTW88: Add support for USB variants Sascha Hauer
2022-11-22 14:52 ` [PATCH v3 01/11] rtw88: print firmware type in info message Sascha Hauer
2022-11-25  8:27   ` Ping-Ke Shih
2022-11-22 14:52 ` [PATCH v3 02/11] rtw88: Call rtw_fw_beacon_filter_config() with rtwdev->mutex held Sascha Hauer
2022-11-25  8:27   ` Ping-Ke Shih
2022-11-22 14:52 ` [PATCH v3 03/11] rtw88: Drop rf_lock Sascha Hauer
2022-11-25  8:29   ` Ping-Ke Shih
2022-11-22 14:52 ` [PATCH v3 04/11] rtw88: Drop h2c.lock Sascha Hauer
2022-11-22 14:52 ` [PATCH v3 05/11] rtw88: Drop coex mutex Sascha Hauer
2022-11-22 14:52 ` [PATCH v3 06/11] rtw88: iterate over vif/sta list non-atomically Sascha Hauer
2022-11-25  8:50   ` Ping-Ke Shih
2022-11-22 14:52 ` [PATCH v3 07/11] rtw88: Add common USB chip support Sascha Hauer
2022-11-28  2:00   ` Ping-Ke Shih
2022-11-28 10:30     ` Sascha Hauer [this message]
2022-11-28 13:41       ` Kalle Valo
2022-11-22 14:52 ` [PATCH v3 08/11] rtw88: Add rtw8821cu chipset support Sascha Hauer
2022-11-23  3:38   ` kernel test robot
2022-11-28  2:13   ` Ping-Ke Shih
2022-11-22 14:52 ` [PATCH v3 09/11] rtw88: Add rtw8822bu " Sascha Hauer
2022-11-28  5:39   ` Ryan Finnie
2022-11-22 14:52 ` [PATCH v3 10/11] rtw88: Add rtw8822cu " Sascha Hauer
2022-11-22 14:52 ` [PATCH v3 11/11] rtw88: Add rtw8723du " Sascha Hauer
2022-11-22 14:55 ` [PATCH v3 00/11] RTW88: Add support for USB variants Sascha Hauer
2022-11-24  6:48   ` Ping-Ke Shih
2022-11-24  8:21     ` Sascha Hauer
2022-11-24  8:26       ` Ping-Ke Shih
2022-11-24  8:36         ` Sascha Hauer
2022-11-24  8:33       ` Kalle Valo
2022-11-24  9:20       ` Sascha Hauer
2022-11-28  3:45 ` Ping-Ke Shih

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=20221128103000.GC29728@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=alex@appudo.com \
    --cc=da@libre.computer \
    --cc=g0000ga@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kernel@pengutronix.de \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@ulli-kroll.de \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neo_jou@realtek.com \
    --cc=neojou@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=phhuang@realtek.com \
    --cc=pkshih@realtek.com \
    --cc=tony0620emma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.