From: Ping-Ke Shih <pkshih@realtek.com>
To: "Marcin Ślusarz" <marcin.slusarz@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Marcin Ślusarz" <mslusarz@renau.com>
Subject: RE: [PATCH] wifi: rtw88/usb: stop rx work before potential power off
Date: Mon, 17 Jun 2024 01:47:35 +0000 [thread overview]
Message-ID: <097ff1363057466ca61aa4f88cc91f9e@realtek.com> (raw)
In-Reply-To: <CA+GA0_tK_+Rsj0FAxO-_VXBLLFMoxW9FHsWhL6gEoWaOMKwWrA@mail.gmail.com>
Marcin Ślusarz <marcin.slusarz@gmail.com> wrote:
> wt., 4 cze 2024 o 02:57 Ping-Ke Shih <pkshih@realtek.com> napisał(a):
> >
> > Marcin Ślusarz <marcin.slusarz@gmail.com> wrote:
> > > --- a/drivers/net/wireless/realtek/rtw88/main.c
> > > +++ b/drivers/net/wireless/realtek/rtw88/main.c
> > > @@ -1357,7 +1357,7 @@ static int rtw_power_on(struct rtw_dev *rtwdev)
> > > int ret;
> > >
> > > if (rtwdev->always_power_on && test_bit(RTW_FLAG_POWERON, rtwdev->flags))
> > > - return 0;
> > > + goto success;
> >
> > rtw_hci_start_rx(rtwdev) is only needed by this case, so
> >
> > if (rtwdev->always_power_on && test_bit(RTW_FLAG_POWERON, rtwdev->flags)) {
> > rtw_hci_start_rx(rtwdev);
> > return 0;
> > }
>
> Yes, strictly speaking, it's needed only in the always_power_on case,
> but doing that in the common code path ensures that it's tested and
> still works.
For the non- always_power_on case, it calls rtw_hci_start()/rtw_hci_stop() already
so I don't think we should call these duplicates.
next prev parent reply other threads:[~2024-06-17 1:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 17:34 wifi: rtw88: 8821CU hangs after some number of power-off/on cycles Marcin Ślusarz
2024-05-27 17:34 ` [PATCH 1/2] wifi: rtw88: use RTW_FLAG_RUNNING for deciding whether to enter/leave IPS Marcin Ślusarz
2024-05-28 3:56 ` Ping-Ke Shih
2024-05-28 10:53 ` Marcin Ślusarz
2024-05-27 17:34 ` [PATCH 2/2] wifi: rtw88: disable power offs for 8821C Marcin Ślusarz
2024-05-27 18:43 ` wifi: rtw88: 8821CU hangs after some number of power-off/on cycles Bitterblue Smith
2024-05-28 10:42 ` Marcin Ślusarz
2024-05-28 12:25 ` Bitterblue Smith
2024-05-28 12:38 ` Marcin Ślusarz
2024-05-28 3:52 ` Ping-Ke Shih
2024-05-28 10:52 ` Marcin Ślusarz
2024-05-29 1:52 ` Ping-Ke Shih
2024-05-29 15:53 ` Marcin Ślusarz
2024-05-30 3:13 ` Ping-Ke Shih
2024-06-03 14:52 ` Marcin Ślusarz
2024-06-03 14:55 ` [PATCH] wifi: rtw88/usb: stop rx work before potential power off Marcin Ślusarz
2024-06-04 0:57 ` Ping-Ke Shih
2024-06-14 11:35 ` Marcin Ślusarz
2024-06-14 12:13 ` [PATCH v2 1/2] wifi: rtw88: 8821cu: keep power on always for 8821CU Marcin Ślusarz
2024-06-14 12:13 ` [PATCH v2 2/2] wifi: rtw88/usb: stop rx work before potential power off Marcin Ślusarz
2024-06-17 1:56 ` Ping-Ke Shih
2024-06-17 1:40 ` [PATCH v2 1/2] wifi: rtw88: 8821cu: keep power on always for 8821CU Ping-Ke Shih
2024-06-17 1:47 ` Ping-Ke Shih [this message]
2024-06-03 14:56 ` [PATCH] wifi: rtw88: usb: drop rx skbs when device is not running Marcin Ślusarz
2024-06-04 0:50 ` wifi: rtw88: 8821CU hangs after some number of power-off/on cycles Ping-Ke Shih
2024-06-14 11:42 ` Marcin Ślusarz
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=097ff1363057466ca61aa4f88cc91f9e@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=mslusarz@renau.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;
as well as URLs for NNTP newsgroup(s).