From: Michael Buesch <mb@bu3sch.de>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 6/7] p54: refractor beacon_update and stop path
Date: Fri, 6 Mar 2009 16:38:16 +0100 [thread overview]
Message-ID: <200903061638.16207.mb@bu3sch.de> (raw)
In-Reply-To: <200903052133.32337.chunkeey@web.de>
On Thursday 05 March 2009 21:33:32 Christian Lamparter wrote:
> According to the LMAC API Section 3.2.2, we don't have to cancel the previous
> beacon manually. The firmware will automatically return it to the driver
> through the feedback mechanism.
> And while we're at it, we can remove some left over code as well.
>
> Signed-off-by: Christian Lamparter <chunkeey@web.de>
> ---
> diff -Nurp a/drivers/net/wireless/p54/p54common.c b/drivers/net/wireless/p54/p54common.c
> --- a/drivers/net/wireless/p54/p54common.c 2009-03-05 15:42:57.000000000 +0100
> +++ b/drivers/net/wireless/p54/p54common.c 2009-03-05 15:50:10.000000000 +0100
> @@ -2015,18 +2015,14 @@ static int p54_beacon_update(struct ieee
> struct sk_buff *beacon;
> int ret;
>
> - if (priv->cached_beacon) {
> - p54_tx_cancel(dev, priv->cached_beacon);
> - /* wait for the last beacon the be freed */
> - msleep(10);
> - }
> -
> beacon = ieee80211_beacon_get(dev, vif);
> if (!beacon)
> return -ENOMEM;
> ret = p54_beacon_tim(beacon);
> if (ret)
> return ret;
> +
> + /* the firmware will automatically cancel old beacons. */
> ret = p54_tx(dev, beacon);
> if (ret)
> return ret;
> @@ -2072,17 +2068,21 @@ out:
> static void p54_stop(struct ieee80211_hw *dev)
> {
> struct p54_common *priv = dev->priv;
> - struct sk_buff *skb;
>
> mutex_lock(&priv->conf_mutex);
> priv->mode = NL80211_IFTYPE_UNSPECIFIED;
> + p54_setup_mac(dev);
> cancel_delayed_work_sync(&priv->work);
> - if (priv->cached_beacon)
> - p54_tx_cancel(dev, priv->cached_beacon);
> +
> + /*
> + * p54spi uses mac80211's workqueue to write the frames into
> + * device's memory. Therefore, we should give the queue a chance
> + * to complete all outstanding work, before the device is stopped.
> + */
> + msleep(25);
What about flush_workqueue()?
But is it even possible for the work to execute here? Does the work take
the conf_mutex?
>
> priv->stop(dev);
> - while ((skb = skb_dequeue(&priv->tx_queue)))
> - kfree_skb(skb);
> + skb_queue_purge(&priv->tx_queue);
> priv->cached_beacon = NULL;
> priv->tsf_high32 = priv->tsf_low32 = 0;
> mutex_unlock(&priv->conf_mutex);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Greetings, Michael.
next prev parent reply other threads:[~2009-03-06 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 20:33 [PATCH 6/7] p54: refractor beacon_update and stop path Christian Lamparter
2009-03-06 15:38 ` Michael Buesch [this message]
2009-03-17 19:59 ` John W. Linville
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=200903061638.16207.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.