b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bu3sch.de>
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH] bcmai: introduce AI driver
Date: Thu, 07 Apr 2011 09:54:46 +0200	[thread overview]
Message-ID: <1302162886.10725.4.camel@maggie> (raw)
In-Reply-To: <BANLkTinfM0QLFwcKZXfWQ_jNYfBJg_et-Q@mail.gmail.com> (sfid-20110406_205435_519066_856A6627)

On Thu, 2011-04-07 at 02:54 +0200, Rafa? Mi?ecki wrote: 
> W dniu 7 kwietnia 2011 02:00 u?ytkownik George Kashperko
> <george@znau.edu.ua> napisa?:
> > For PCI function description take a look at PCI specs or PCI
> > configuration space description (e. g.
> > http://en.wikipedia.org/wiki/PCI_configuration_space)
> >
> > Sorry for missleading short-ups, w11 - bcm80211 core, under two-head I
> > mean ssb/axi with two functional cores on same interconnect (like w11
> > +w11, not a lot of these exists I guess). Also there were some b43+b44
> > on single PCI ssb host and those where implemented as ssb interconnect
> > on multifunctional PCI host therefore providing separate access windows
> > for each function.
> >
> > Might I mussunderstood something (its late night here at my place) when
> > you where talking about using coreswitching involved for two drivers
> > therefore I remembered about those functions. Seems now you were talking
> > about chipcommon+b43 access sharing same window.
> >
> > As for core switching requirments for earlier SSB interconnects on PCI
> > hosts where there were no direct chipcommon access, that one can be
> > accomplished without spin_lock/mutex for b43 or b44 cores with proper
> > bus design.
> >
> > AXI doesn't need spinlocks/mutexes as both chipcommon and pci bridge are
> > available directly and b43 will be the only one requiring window access.
> 
> Ahh, so while talking about 4 windows, I guess you counted fixes
> windows as well. That would be right, matching my knowledge.
> 
> When asking question about amount of cores we may want to use
> simultaneously I didn't think about ChipCommon or PCIe. The real
> problem would be to support for example two 802.11 cores and one
> ethernet core at the same time. That gives us 3 cores while we have
> only 2 sliding windows.

Would that really be a problem? Think of it. This combination 
will only be available on embedded devices. But do we have windows
on embedded devices? I guess not. If AXI is similar to SSB, the MMIO
of all cores will always be mapped. So accesses can be done
without switch or lock.

I do really think that engineers at broadcom are clever enough
to design a hardware that does not require expensive window sliding
all the time while operating.

-- 
Greetings Michael.

  reply	other threads:[~2011-04-07  7:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 19:57 [RFC][PATCH] bcmai: introduce AI driver Rafał Miłecki
2011-04-05 19:25 ` Rafał Miłecki
2011-04-05 19:29 ` Michael Büsch
     [not found] ` <1302032137.3969.10.camel@Joe-Laptop>
2011-04-05 20:15   ` Rafał Miłecki
2011-04-05 20:25     ` Michael Büsch
2011-04-05 20:50     ` Larry Finger
     [not found] ` <op.vtisojsk3ri7v4@arend-laptop>
2011-04-06 18:02   ` Rafał Miłecki
     [not found]     ` <op.vti9ote53ri7v4@arend-laptop>
2011-04-06 20:40       ` Rafał Miłecki
2011-04-06 20:42         ` Rafał Miłecki
2011-04-06 20:57           ` Michael Büsch
2011-04-06 21:01             ` Rafał Miłecki
2011-04-06 21:08               ` Michael Büsch
2011-04-06 21:12                 ` Rafał Miłecki
2011-04-06 21:20                   ` Michael Büsch
     [not found]                   ` <1302124737.27258.7.camel@dev.znau.edu.ua>
2011-04-06 23:20                     ` Rafał Miłecki
     [not found]                       ` <1302134429.27258.32.camel@dev.znau.edu.ua>
2011-04-07  0:54                         ` Rafał Miłecki
2011-04-07  7:54                           ` Michael Büsch [this message]
2011-04-07  9:55                             ` Rafał Miłecki
2011-04-08 16:56   ` Rafał Miłecki
2011-04-08 17:09     ` Rafał Miłecki
2011-04-08 17:14       ` Rafał Miłecki
     [not found]     ` <op.vtmqm7fw3ri7v4@arend-laptop>
2011-04-08 17:27       ` Rafał Miłecki
     [not found]         ` <op.vtmqujir3ri7v4@arend-laptop>
2011-04-08 17:31           ` Rafał Miłecki
     [not found]   ` <20110410080159.GB2798@ucw.cz>
2011-04-10  8:05     ` Rafał Miłecki
     [not found]       ` <20110410082420.GA1460@localhost.ucw.cz>
2011-04-10  8:30         ` Rafał Miłecki
     [not found]           ` <op.vtpt6v173ri7v4@arend-laptop>
2011-04-10 11:32             ` Rafał Miłecki

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=1302162886.10725.4.camel@maggie \
    --to=mb@bu3sch.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).