linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org,
	Stefano Brivio <stefano.brivio@polimi.it>
Subject: Re: [PATCH v2] b43: Add fastpath to b43_mac_suspend()
Date: Wed, 16 Apr 2008 21:13:05 +0200	[thread overview]
Message-ID: <200804162113.05549.mb@bu3sch.de> (raw)
In-Reply-To: <1208370999.11676.60.camel@johannes.berg>

On Wednesday 16 April 2008 20:36:39 Johannes Berg wrote:
> On Tue, 2008-04-15 at 21:13 +0200, Michael Buesch wrote:
> > This adds a fastpath for the common workloads to the
> > MAC suspend flushing.
> 
> 
> > @@ -2340,12 +2340,20 @@ static void b43_mac_suspend(struct b43_w
> >  		b43_power_saving_ctl_bits(dev, B43_PS_AWAKE);
> >  		b43_write32(dev, B43_MMIO_MACCTL,
> >  			    b43_read32(dev, B43_MMIO_MACCTL)
> >  			    & ~B43_MACCTL_ENABLED);
> >  		/* force pci to flush the write */
> >  		b43_read32(dev, B43_MMIO_MACCTL);
> > +		/* Finally wait for the microcode to flush the fifos. */
> 
> That comment is wrong, the ucode won't flush the FIFOs, it'll just go to
> sleep. If you want it to flush FIFOs you have to set a flush request bit
> somewhere (mac command I think), but you don't actually, you just don't
> want to have it processing stuff.

Ah yeah. Whatever. What was meant it it flushes everything from the host
point of view and goes to sleep. Feel free to remove that comment, John.
(simply remove the line from the patch before applying it).

-- 
Greetings Michael.

      reply	other threads:[~2008-04-16 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 19:13 [PATCH v2] b43: Add fastpath to b43_mac_suspend() Michael Buesch
2008-04-16 18:36 ` Johannes Berg
2008-04-16 19:13   ` Michael Buesch [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=200804162113.05549.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=stefano.brivio@polimi.it \
    /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).