Return-path: Received: from mail-qy0-f174.google.com ([209.85.216.174]:61664 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753546Ab1DWMdm (ORCPT ); Sat, 23 Apr 2011 08:33:42 -0400 MIME-Version: 1.0 In-Reply-To: References: <1303331669-31293-1-git-send-email-arend@broadcom.com> <201104211612.49805.arnd@arndb.de> From: Jonas Gorski Date: Sat, 23 Apr 2011 14:33:21 +0200 Message-ID: Subject: Re: [PATCH] drivers: brcmaxi: provide amba axi functionality in separate module To: Arend van Spriel Cc: Arnd Bergmann , "zajec5@gmail.com" , "linux-kernel@vger.kernel.org" , "linux-wireless@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "b43-dev@lists.infradead.org" , George Kashperko , Hauke Mehrtens , Russell King , Larry Finger , Andy Botting , Greg KH , Michael Buesch Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 21 April 2011 16:38, Arend van Spriel wrote: > Would it be possible to make chipcommon driver optional (not doing the > initialization)? This would need to be done on a per-device/bus basis, at least for embedded. Consider the following setup (which is quite common for dual band routers): BCM4718 +- Common Core <- provides flash write access, GPIOs, watchdog, ... +- 802.11 Core <- for 2.4Ghz wifi +- PCIe Core + BCM43224 +- Common Core +- 802.11 Core <- for 5Ghz wifi (I omitted any cores not relevant for the example) So eventually you want to able to drive both 802.11 cores, but can't exclusively claim both common cores. Regards Jonas