Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755061Ab1DWPHs (ORCPT ); Sat, 23 Apr 2011 11:07:48 -0400 Received: from mms2.broadcom.com ([216.31.210.18]:1732 "EHLO mms2.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754806Ab1DWPHq convert rfc822-to-8bit (ORCPT ); Sat, 23 Apr 2011 11:07:46 -0400 X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031 To: "Jonas Gorski" 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" Subject: Re: [PATCH] drivers: brcmaxi: provide amba axi functionality in separate module References: <1303331669-31293-1-git-send-email-arend@broadcom.com> <201104211612.49805.arnd@arndb.de> Date: Sat, 23 Apr 2011 17:07:19 +0200 MIME-Version: 1.0 From: "Arend van Spriel" Organization: Broadcom Message-ID: In-Reply-To: User-Agent: Opera Mail/11.10 (Linux) X-WSS-ID: 61AC347A3CK20952215-01-01 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1631 Lines: 47 On Sat, 23 Apr 2011 14:33:21 +0200, Jonas Gorski wrote: > 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 (bus A) +- MIPS74k > +- Common Core <- provides flash write access, GPIOs, watchdog, ... > +- 802.11 Core <- for 2.4Ghz wifi > +- PCIe Core > + BCM43224 (bus B) > +- Common Core > +- 802.11 Core <- for 5Ghz wifi > > (I omitted any cores not relevant for the example) The MIPS may be relevant as well ;-) In the example above I would expect two axi bus driver instances for bus A and bus B. > So eventually you want to able to drive both 802.11 cores, but can't > exclusively claim both common cores. I would expect to be probed twice. One call for 2.4GHz 802.11 core referencing to bus A and one call for 5GHz 802.11 core referencing to bus B. Regarding chipcommon I agree that it requires one init sequence per device. I would just like to have the option to provide a custom initialization function for chip common (and possibly pcie) somehow. Gr. AvS -- "The world is indeed comic, but the joke is on mankind." — H.P. Lovecraft -- 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/