linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: bcma usage in isr context
Date: Mon, 5 Dec 2011 16:27:08 +0100	[thread overview]
Message-ID: <4EDCE2CC.3060500@broadcom.com> (raw)
In-Reply-To: <CACna6rznu8d1BjG0EWjP1VRCPdYAGJv1q+fi1X+XF_Bf-Cx+Mg@mail.gmail.com>

On 12/05/2011 12:30 PM, Rafał Miłecki wrote:
> Hi,
> 
> Sorry for late reply, I was a little busy recently...
> 
> W dniu 1 grudnia 2011 14:09 użytkownik Arend van Spriel
> <arend@broadcom.com> napisał:
>> I am doing some final testing on our brcmsmac driver, which I tinkered
>> to become a bcma device driver. During testing an issue popped up in the
>> ISR code.
> 
> Do you mean interrupts code?

Yep. ISR stands for 'interrupt service routine'.

>> Looking into the bcma read/write functions in host_pci.c I conclude that
>> bcma itself does not provide protection for concurrency. Am I correct in
>> that? How is this solved in b43?
> 
> I think I mean the fact that core driver can switch BCMA to
> ChipCommon, while interrupt handler will try to access 80211 core?

That is indeed what I mean.

> You're right, we don't handle this properly. I'll try to send patch
> today to make use of fixed windows. I've it here for some time
> already, just didn't clean it enough.
> 

Ok. For now I have a patch in the bcma read/write host_pci functions
that solves it, but fixed bar windows are preferable.

Gr. AvS


  reply	other threads:[~2011-12-05 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 13:09 bcma usage in isr context Arend van Spriel
2011-12-05 11:30 ` Rafał Miłecki
2011-12-05 15:27   ` Arend van Spriel [this message]
2011-12-07 12:52     ` Rafał Miłecki
2011-12-07 14:01       ` Arend van Spriel
2011-12-07 15:06         ` Rafał Miłecki
2011-12-09 17:37           ` Arend van Spriel

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=4EDCE2CC.3060500@broadcom.com \
    --to=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --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).