Re: [RFC 13/14] irq_domain: Remove 'new' irq_domain in favour of the ppc one
From: Grant Likely <hidden>
Date: 2012-01-11 21:27:40
Also in:
lkml
From: Grant Likely <hidden>
Date: 2012-01-11 21:27:40
Also in:
lkml
On Wed, Jan 11, 2012 at 2:15 PM, Rob Herring [off-list ref] wrote:
Grant, On 01/11/2012 02:22 PM, Grant Likely wrote:quoted
This patch removes the simplistic implementation of irq_domains and enab=
les
quoted
the powerpc infrastructure for all irq_domain users. =A0The powerpc infrastructure includes support for complex mappings between Linux and hardware irq numbers, and can manage allocation of irq_descs. This patch also converts the few users of irq_domain_add()/irq_domain_de=
l()
quoted
to call irq_domain_add_legacy() instead.So what is the non-legacy way? Legacy implies we don't want to do it that way. I guess until we remove all non-DT platforms with GIC we are stuck with legacy. That seems like it could be a ways out until we get there.
Non-legacy is letting the irq_domain manage the irq_desc allocations. Some of the controllers will be easy to convert, some will be more difficult. The primary thing that really blocks getting away from the legacy method is anything that expects hardcoded #defined irq numbers. The goal is to convert all users over to the linear revmap method. g.