[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1507202326450.18576@nanos>
Date: Mon, 20 Jul 2015 23:28:17 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
cc: marc.zyngier@....com, lorenzo.pieralisi@....com,
hanjun.guo@...aro.org, tomasz.nowicki@...aro.org,
rjw@...ysocki.net, al.stone@...aro.org, catalin.marinas@....com,
will.deacon@....com, msalter@...hat.com, grant.likely@...aro.org,
leo.duran@....com, sherry.hurwitz@....com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org
Subject: Re: [RFCv2 PATCH 1/8] irqdomain: Introduce
irq_domain_ops.init_alloc_info
On Mon, 13 Jul 2015, Suravee Suthikulpanit wrote:
> Currently, when calling irq_domain_alloc_irqs() on ARM64, it uses
> struct of_phandle_args to pass irq information. However, this is not
> appropriate for ACPI since of_phandle_args is specific to DT.
>
> Therefore, this patch introduces a new function pointer,
> irq_domain_ops.init_alloc_info, which can be used by irqchips to provide
> a way to initialize irqchip-specific data-structure for allocating IRQ.
>
> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
> ---
> NOTE:
> Similarly, x86 is currently using struct irq_alloc_info
> (see arch/x86/include/asm/hw_irq.h) and each irq_domain has different
> way of initializing this structure.
And why don't you use the same mechanism on ARM and have a private
irq_alloc_info implementation which can carry either DT or ACPI
information?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists