[RFC][PATCH] bcmai: introduce AI driver

George Kashperko george at znau.edu.ua
Sun Apr 10 12:11:57 EDT 2011


> On Sun, 10 Apr 2011 10:30:53 +0200, Rafał Miłecki <zajec5 at gmail.com> wrote:
> 
> > 2011/4/10 Pavel Machek <pavel at ucw.cz>:
> >>> >> >+config BCMAI_HOST_PCI_POSSIBLE
> >>> >> >+       bool
> >>> >> >+       depends on BCMAI && PCI = y
> >>> >> >+       default y
> >>> >> >+
> >>> >> >+config BCMAI_HOST_PCI
> >>> >> >+       bool "Support for AI on PCI-host bus"
> >>> >> >+       depends on BCMAI_HOST_PCI_POSSIBLE
> >>> >> >+
> 
> Hi Rafał,
> 
> Could use term AMBA AXI instead which gives enough hits on Google to hint  
> interested people to more in depth information.
> 
> FYI: AXI = Advanced eXtensible Interface
> 	High-speed interconnect for chip cores ( provides higher bursts/transfers  
> than predecessor AHB = Advanced High-performance Bus (AHB)).
> 
> Gr. AvS

Not sure if AXI will be relevant bus name to manage newer Broadcom IP
cores. Yes, AMBA AXI is underlying interconnect used for communications,
but those communications are made in regard of communication ports
(those thingys referenced at Broadcom code as wrappers and which are
actually master ports intermediately bound to the backplane itself).
Pretty much sure your original bcmb is much more relevant for managing
Broadcom hardware extensions over AXI than just axi, especially
considering that techniques we use to identify, enumerate and control
AXI slave ports are completely Broadcom-specific.

Have nice day,
George





More information about the linux-arm-kernel mailing list