From: Michael Straube <straube.linux@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Phillip Potter <phil@philpotter.co.uk>,
"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: staging: r8188eu: how to handle nested mutex under spinlock
Date: Sun, 3 Apr 2022 10:44:46 +0200 [thread overview]
Message-ID: <6a1d7485-d405-d9a6-fefd-5a10d038d493@gmail.com> (raw)
In-Reply-To: <d9c7a2ba-288a-d81a-cd59-5b002489d821@lwfinger.net>
On 4/2/22 23:32, Larry Finger wrote:
> In drivers/net/wireless/realtek/rtlwifi, we had a similar problem. There
> it was handled by putting the lps_enter() and lps_leave() operations in
> a separate workqueue. In this case, the routines were rtl_lps_enter()
> and rtl_lps_leave(). Each of them sets a variable to indicate whether
> enter_ps is true or false, and schedules the workqueue. In the
> workqueue's callback routine, the routines to start/stop ps mode are
> called. The code is in drivers/net/wireless/realtek/rtlwifi/ps.c.
>
> This solution is only one of many, and there may be a better one.
>
> Larry
>
Thank you for the explanation Larry.
Michael
next prev parent reply other threads:[~2022-04-03 8:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 20:47 Michael Straube
2022-04-02 21:13 ` Pavel Skripkin
2022-04-02 21:32 ` Larry Finger
2022-04-03 8:44 ` Michael Straube [this message]
[not found] ` <4389354.LvFx2qVVIh@leap>
[not found] ` <1813843.tdWV9SEqCh@leap>
2022-04-03 11:08 ` Michael Straube
[not found] ` <7365301.EvYhyI6sBW@leap>
2022-04-03 11:41 ` Michael Straube
2022-04-03 11:48 ` Pavel Skripkin
[not found] ` <1817830.CQOukoFCf9@leap>
2022-04-03 12:14 ` Michael Straube
2022-04-03 12:19 ` Pavel Skripkin
[not found] ` <4412825.cEBGB3zze1@leap>
2022-04-03 12:45 ` Pavel Skripkin
[not found] ` <2029549.KlZ2vcFHjT@leap>
2022-04-03 13:02 ` Pavel Skripkin
2022-04-03 20:51 ` Michael Straube
2022-04-03 21:15 ` Pavel Skripkin
2022-04-04 8:50 ` David Laight
2022-04-04 16:38 ` Pavel Skripkin
2022-04-04 16:59 ` David Laight
2022-04-04 17:12 ` Pavel Skripkin
[not found] ` <1858641.taCxCBeP46@leap>
[not found] ` <2366209.jE0xQCEvom@leap>
2022-04-03 12:18 ` Michael Straube
2022-04-04 13:33 ` Dan Carpenter
2022-04-04 14:16 ` Michael Straube
[not found] ` <3097543.5fSG56mABF@leap>
2022-04-03 11:44 ` Michael Straube
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=6a1d7485-d405-d9a6-fefd-5a10d038d493@gmail.com \
--to=straube.linux@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
/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
all inboxes | Powered by JetHome®