From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arend van Spriel Subject: Re: [PATCH v2 1/2] bcma: register bcma as device tree driver Date: Thu, 18 Sep 2014 11:42:28 +0200 Message-ID: <541AA904.1070002@broadcom.com> References: <1410904582-6519-1-git-send-email-hauke@hauke-m.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Hauke Mehrtens , John Linville , "linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , Arnd Bergmann , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org On 09/17/14 17:10, Rafa=C5=82 Mi=C5=82ecki wrote: > On 16 September 2014 23:56, Hauke Mehrtens wrote: >> This driver is used by the bcm53xx ARM SoC code. Now it is possible = to >> give the address of the chipcommon core in device tree and bcma will >> search for all the other cores. > > Did you get any answer from Arend about detecting IRQs? > > If not: > Arend: how much time it make take you to get an answer? I already discussed this with our chip architect. There is a chip desig= n=20 rule that core index corresponds to the irq number. This at least is=20 true for the bcm43xx devices, but unsure about others. So that option=20 does not seem to fit. That leaves the OOB_ROUTER core I mentioned=20 earlier, but it is a chip designers nightmare as they told me. Did not=20 sound encouraging enough to start digging in there to obtain the=20 information. Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html