From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Arend van Spriel" <arend@broadcom.com>,
"Rafał Miłecki" <zajec5@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] bcma: register bcma as device tree driver
Date: Thu, 18 Sep 2014 22:50:25 +0200 [thread overview]
Message-ID: <541B4591.3010208@hauke-m.de> (raw)
In-Reply-To: <541AA904.1070002@broadcom.com>
On 09/18/2014 11:42 AM, Arend van Spriel wrote:
> On 09/17/14 17:10, Rafał Miłecki wrote:
>> On 16 September 2014 23:56, Hauke Mehrtens<hauke@hauke-m.de> 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 design
> rule that core index corresponds to the irq number. This at least is
> true for the bcm43xx devices, but unsure about others. So that option
> does not seem to fit. That leaves the OOB_ROUTER core I mentioned
> earlier, but it is a chip designers nightmare as they told me. Did not
> sound encouraging enough to start digging in there to obtain the
> information.
Thanks for asking around.
I will go with specifying the IRQs in device tree then.
Hauke
next prev parent reply other threads:[~2014-09-18 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 21:56 [PATCH v2 1/2] bcma: register bcma as device tree driver Hauke Mehrtens
2014-09-16 21:56 ` [PATCH v2 2/2] bcma: get IRQ numbers from dt Hauke Mehrtens
2014-09-17 15:10 ` [PATCH v2 1/2] bcma: register bcma as device tree driver Rafał Miłecki
2014-09-18 9:42 ` Arend van Spriel
2014-09-18 20:50 ` Hauke Mehrtens [this message]
2014-09-18 20:03 ` Rafał Miłecki
2014-09-18 20:52 ` Hauke Mehrtens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541B4591.3010208@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arend@broadcom.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).