From: Luciano Coelho <coelho@ti.com>
To: Ido Yariv <ido@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl12xx: Restart TX when TX descriptors are available
Date: Fri, 29 Apr 2011 23:05:43 +0300 [thread overview]
Message-ID: <1304107543.12586.160.camel@cumari> (raw)
In-Reply-To: <1303134251-31514-1-git-send-email-ido@wizery.com>
On Mon, 2011-04-18 at 16:44 +0300, Ido Yariv wrote:
> The driver stops sending TX packets when either there aren't enough
> memory blocks, or it runs out of TX descriptors. The driver continues to
> send packets to the FW only when more memory blocks are available.
>
> The FW might free TX descriptors without freeing the corresponding
> memory blocks, especially when dynamic memory is enabled. In cases where
> memory blocks are not freed at all, the driver will keep waiting for
> more memory blocks indefinitely.
>
> Fix this by clearing the WL1271_FLAG_FW_TX_BUSY flag when there are
> available TX descriptors.
>
> Signed-off-by: Ido Yariv <ido@wizery.com>
> ---
Thanks, Ido. Applied.
--
Cheers,
Luca.
prev parent reply other threads:[~2011-04-29 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 13:44 [PATCH] wl12xx: Restart TX when TX descriptors are available Ido Yariv
2011-04-29 20:05 ` Luciano Coelho [this message]
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=1304107543.12586.160.camel@cumari \
--to=coelho@ti.com \
--cc=ido@wizery.com \
--cc=linux-wireless@vger.kernel.org \
/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