linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Arend van Spriel" <arend@broadcom.com>,
	"Scott Sanbar" <scott.sanbar@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: Re: BCM4331 fails to associate after suspend
Date: Mon, 6 Feb 2012 16:34:47 -0600	[thread overview]
Message-ID: <20120206223447.GE31938@ubuntu-macmini> (raw)
In-Reply-To: <4F302647.2070102@hauke-m.de>

On Mon, Feb 06, 2012 at 08:13:11PM +0100, Hauke Mehrtens wrote:
> On 02/06/2012 06:37 PM, Seth Forshee wrote:
> > On Mon, Feb 06, 2012 at 05:56:20PM +0100, Rafał Miłecki wrote:
> >> 2012/2/4 Seth Forshee <seth.forshee@canonical.com>:
> >>> On Sat, Feb 04, 2012 at 11:44:23AM +0100, Arend van Spriel wrote:
> >>>> On 02/03/2012 11:28 PM, Seth Forshee wrote:
> >>>>>
> >>>>> I've been looking around a bit in the b43 and bcma drivers, but so far I
> >>>>> haven't found the reason why this happens. Any help would be
> >>>>> appreciated. Let me know if there's additional information I can
> >>>>> provide.
> >>>>>
> >>>>
> >>>> With which kernel version do you see these issues? BCMA suspend/resume
> >>>> code has a fix in 3.3-rc1. So if you are seeing it on a 3.2 kernel,
> >>>> please give it a try.
> >>>
> >>> I've tried 3.3-rc2 and the wirless-testing tree, and the problem still
> >>> exists in both.
> >>
> >> I don't have access to suspendable machine with Mini PCIe card, not to
> >> mention BCM4331 which is available for Mac-specific slot only (or
> >> routers as embedded wifi). It may be b43 needs to fix but I'm not
> >> really able to work on that. Plus the whole BCM4331 code is really
> >> tricky, as it comes from RE based on dumps only :(
> > 
> > Okay, I'll keep poking at it to see if I can come up with anything. If
> > you've got any suggestions on things I should be looking at or trying,
> > I'm all ears.
> > 
> > Seth
> 
> According to the Broadcom SDK for SoCs bcma_pcicore_serdes_workaround()
> should be called when coming out of standby/hibernate.
> The code wl uses to do the same thing as bcma does is open source. You
> find it in the GPL package of many Broadcom based Wifi Routers.

Thanks for the suggestion. Unfortunately calling
bcma_pcicore_serdes_workaround() during resume doesn't help. I'll look
at the wl code to see if I can learn anything there.

Seth

  reply	other threads:[~2012-02-06 22:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 22:28 BCM4331 fails to associate after suspend Seth Forshee
2012-02-03 22:37 ` John Schoenick
2012-02-04 10:44 ` Arend van Spriel
2012-02-04 14:25   ` Seth Forshee
2012-02-06 16:56     ` Rafał Miłecki
2012-02-06 17:37       ` Seth Forshee
2012-02-06 19:13         ` Hauke Mehrtens
2012-02-06 22:34           ` Seth Forshee [this message]
2012-02-07  7:04             ` Rafał Miłecki
2012-02-07  7:08               ` Rafał Miłecki
2012-02-07 15:29                 ` Seth Forshee
2012-02-16 14:55                   ` Seth Forshee

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=20120206223447.GE31938@ubuntu-macmini \
    --to=seth.forshee@canonical.com \
    --cc=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=scott.sanbar@gmail.com \
    --cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).