From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM/Kernel: Problems with multiple VIC registration
Date: Tue, 05 Feb 2013 08:12:15 -0600 [thread overview]
Message-ID: <5111133F.9050906@gmail.com> (raw)
In-Reply-To: <5110D55F.9040509@st.com>
Adding Linus W.
On 02/05/2013 03:48 AM, Amit Virdi wrote:
> Hi All,
>
> I've picked Linux kernel 3.8-rc4 and added the support for my ARM based
> board in it.
What about rc6? Linus has been fixing some VIC issues in this area.
Rob
> - The SoC has 2 VICs
> - valid_sources are 32 (~0)
> - NR_IRQS is defined as 104; => irq_desc[104]
> - I'm not populating devices thro' DT
>
> The first controller is registered throu' irq_domain_add_linear API. As
> a result of this call, a new domain is allocated to the VIC device.
>
> In the next step IRQ mapping, irq_create_mapping is called and this maps
> all the IRQs in the Linux IRQ space. However in doing so, it uses
> irq_desc[1]...irq_desc[32]. irq_dec[0] is not used (checked using a
> debugger)!
>
> When I'm trying to register the second VIC (it's throu'
> irq_domain_add_legacy), I'm getting warnings since irq_get_irq_data
> returns irq_data of irq_desc[32] which has already been mapped.
>
> In short, irq_domain_add_legacy returns with NULL irq_domain.
>
> I checked that multiple VIC registration works in Linux 3.4
> Is it something that I'm missing while adapting to the new framework, or
> there's some undetected problem?
>
> I've attached the logfile generated with debug prints ON. Would
> appreciate any help...
>
> Thanks
> Amit Virdi
next prev parent reply other threads:[~2013-02-05 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 9:48 ARM/Kernel: Problems with multiple VIC registration Amit Virdi
2013-02-05 14:12 ` Rob Herring [this message]
2013-02-06 4:23 ` Amit Virdi
2013-02-05 16:27 ` Linus Walleij
2013-02-06 3:52 ` Amit Virdi
2013-02-06 9:15 ` Linus Walleij
2013-02-12 12:38 ` Amit Virdi
2013-02-12 13:11 ` Linus Walleij
2013-02-13 9:18 ` Amit Virdi
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=5111133F.9050906@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).