From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Nikolay Nikolov <dobrev666@gmail.com>,
<linux-wireless@vger.kernel.org>, <brcm80211@lists.linux.dev>,
<brcm80211-dev-list.pdl@broadcom.com>,
<nikolay.nikolov@bench.com>
Subject: Re: [PATCH 1/1] wifi: brcm80211: brcmfmac: Prevent sdio bus going to sleep while transfering data
Date: Sun, 07 Jul 2024 15:20:56 +0200 [thread overview]
Message-ID: <1908d5acac0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (raw)
In-Reply-To: <1c6684f6-d3a8-4eaa-842d-c21fa2dd81c1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
On July 7, 2024 2:22:49 PM Nikolay Nikolov <dobrev666@gmail.com> wrote:
> Use mutex to prevent sdio bus to be put to sleep by the sdio_bus_watchdog
> while sdio dataworker handles sdio_dpc data transfers.
Any reason for sending 3 identical patches within the hour.
As to the patch itself I would like to know if there is a reported issue
being fixed here. What is the motivation behind this patch. Looking at the
code I do not think the mutex is needed so please elaborate.
Regards,
Arend
> Signed-off-by: Nikolay Nikolov <nikolay.nikolov@bench.com>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c | 6 ++++++
> 1 file changed, 6 insertions(+)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2024-07-07 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 12:22 [PATCH 1/1] wifi: brcm80211: brcmfmac: Prevent sdio bus going to sleep while transfering data Nikolay Nikolov
2024-07-07 13:20 ` Arend Van Spriel [this message]
2024-07-07 14:37 ` Nikolay Nikolov
2024-07-09 10:12 ` Kalle Valo
2024-07-09 19:27 ` Nikolay Nikolov
-- strict thread matches above, loose matches on Subject: below --
2024-07-07 11:47 Nikolay Nikolov
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=1908d5acac0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=dobrev666@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nikolay.nikolov@bench.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