Hi Mark,
On 2/7/2012 6:28 PM, Mark Brown wrote:
On Tue, Feb 07, 2012 at 12:19:50AM +0100, Cousson, Benoit wrote:
The twl changes were done like that because it was assuming that
USE_OF and thus IRQ_DOMAIN will be enabled by default for all OMAP2+
platforms at 3.3 time. The whole point of doing that was to reduce
the ifdefery in every drivers we have to adapt to DT.
Note that those drivers have been buildable on non-OMAP platforms for a
very long time now in order to give better build coverage for the
function drivers.
Yes, sure, but the only restriction I was adding is to make that driver
dependent of the IRQ_DOMAIN stuff. That should be there by default on
every ARM platform soon and this is there as well for PPC. So this will
still be buildable on other platforms assuming they will support IRQ_DOMAIN.
The point is that once we will fully use the irq_domain support to
generic-chip that Rob is working on for this driver, we will always need
IRQ_DOMAIN enabled.
So far the IRQ_DOMAIN support is minimal and just needed for DT because
that piece of infrastructure was not ready at that time.
Regards,
Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
