Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756652Ab1DGSxK (ORCPT ); Thu, 7 Apr 2011 14:53:10 -0400 Received: from mail.academy.zt.ua ([82.207.120.245]:54396 "EHLO mail.academy.zt.ua" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756608Ab1DGSxH (ORCPT ); Thu, 7 Apr 2011 14:53:07 -0400 X-MDAV-Processed: mail.academy.zt.ua, Thu, 07 Apr 2011 21:53:03 +0300 X-Spam-Processed: mail.academy.zt.ua, Thu, 07 Apr 2011 21:53:03 +0300 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: george@academy.zt.ua X-Return-Path: george@znau.edu.ua X-Envelope-From: george@znau.edu.ua Subject: Re: [RFC][PATCH] bcmai: introduce AI driver From: George Kashperko To: Arend van Spriel Cc: Arnd Bergmann , Russell King , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "b43-dev@lists.infradead.org" , linuxdriverproject , "linux-arm-kernel@lists.infradead.org" , Larry Finger In-Reply-To: References: <1302033463-1846-1-git-send-email-zajec5@gmail.com> <1302123428.20093.6.camel@maggie> <1302124112.20093.11.camel@maggie> <1302124737.27258.7.camel@dev.znau.edu.ua> <1302134429.27258.32.camel@dev.znau.edu.ua> <1302162886.10725.4.camel@maggie> Content-Type: text/plain; charset=UTF-8 Date: Thu, 07 Apr 2011 21:50:40 +0300 Message-Id: <1302202240.30694.16.camel@dev.znau.edu.ua> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2644 Lines: 64 > On Thu, 07 Apr 2011 09:54:46 +0200, Michael Büsch wrote: > > >> 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. > > Agree. For embedded systems there is no need to switch cores. Each core > register space and wrapper register space is mapped. In the brcm80211 we > have the concept of fast versus slow host interface. The criteria for fast > host interface is based on following expression: > > fast_host_bus = (host_bus_coretype == PCIE_CORE_ID) || > ((host_bus_coretype == PCI_CORE_ID) && (host_bus_corerev >= 13)) > > If this is true, chipcommon and pci/pcie registers are accessed without > sliding the window using the fixed offsets Rafał mentioned earlier. The > BAR0 window size is 16KB. Well, the major pci window managing concept in your code isn't really fast switching but rather smart switching. chipcommon and pci bridge core specific processing is well refined in appropriate routines each looking like: irqdisable switchcore(cc_or_pcie) ... code ... switchcore(back) irqenable Thus you always have pci window pointing to the function core and can ioread/iowrite without spinlocking windowed accesses. Yes, you use also "fast" switching for pci rev. >= 13 && pcie avoiding irq(ena|disa) for such a configurations but, as I've mentioned earlier, for axi this is rudimentary from pci rev. < 13 times as both pci bridge and chipcommon are available simultaneously with fixed windows. > > > 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. > > > > If a bigger window is clever enough ;-) > > Gr. AvS Have nice day, George -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/