From: Arend van Spriel <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: "Rafał Miłecki" <zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>,
John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/2] bcma: register bcma as device tree driver
Date: Thu, 18 Sep 2014 11:42:28 +0200 [thread overview]
Message-ID: <541AA904.1070002@broadcom.com> (raw)
In-Reply-To: <CACna6rzGa6wiKTrXbtUSGekRNq7gUkC0kyu4RQ_p4fG0Hd+DjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 09/17/14 17:10, Rafał Miłecki wrote:
> On 16 September 2014 23:56, Hauke Mehrtens<hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org> 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.
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-18 9:42 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
[not found] ` <1410904582-6519-1-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
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
[not found] ` <CACna6rzGa6wiKTrXbtUSGekRNq7gUkC0kyu4RQ_p4fG0Hd+DjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-18 9:42 ` Arend van Spriel [this message]
[not found] ` <541AA904.1070002-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2014-09-18 20:50 ` Hauke Mehrtens
2014-09-18 20:03 ` Rafał Miłecki
[not found] ` <CACna6rw0-g+v6u3Yxhnmy1NT0mhj-s4re5R3z0dbBV-tMvky6Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=541AA904.1070002@broadcom.com \
--to=arend-dy08kvg/lbpwk0htik3j/w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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).