From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: marc.zyngier@arm.com, lorenzo.pieralisi@arm.com,
hanjun.guo@linaro.org, tomasz.nowicki@linaro.org,
rjw@rjwysocki.net, al.stone@linaro.org, catalin.marinas@arm.com,
will.deacon@arm.com, msalter@redhat.com, grant.likely@linaro.org,
leo.duran@amd.com, sherry.hurwitz@amd.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [RFCv2 PATCH 1/8] irqdomain: Introduce irq_domain_ops.init_alloc_info
Date: Thu, 23 Jul 2015 13:50:42 +0700 [thread overview]
Message-ID: <55B08EC2.4000204@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1507202326450.18576@nanos>
On 7/21/15 04:28, Thomas Gleixner wrote:
> 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@amd.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?
Let me look further into this. I would like to take a similar approach here.
Suravee
> Thanks,
>
> tglx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: Suravee.Suthikulpanit@amd.com (Suravee Suthikulpanit)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFCv2 PATCH 1/8] irqdomain: Introduce irq_domain_ops.init_alloc_info
Date: Thu, 23 Jul 2015 13:50:42 +0700 [thread overview]
Message-ID: <55B08EC2.4000204@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1507202326450.18576@nanos>
On 7/21/15 04:28, Thomas Gleixner wrote:
> 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@amd.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?
Let me look further into this. I would like to take a similar approach here.
Suravee
> Thanks,
>
> tglx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: <marc.zyngier@arm.com>, <lorenzo.pieralisi@arm.com>,
<hanjun.guo@linaro.org>, <tomasz.nowicki@linaro.org>,
<rjw@rjwysocki.net>, <al.stone@linaro.org>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>,
<msalter@redhat.com>, <grant.likely@linaro.org>,
<leo.duran@amd.com>, <sherry.hurwitz@amd.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Subject: Re: [RFCv2 PATCH 1/8] irqdomain: Introduce irq_domain_ops.init_alloc_info
Date: Thu, 23 Jul 2015 13:50:42 +0700 [thread overview]
Message-ID: <55B08EC2.4000204@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1507202326450.18576@nanos>
On 7/21/15 04:28, Thomas Gleixner wrote:
> 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@amd.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?
Let me look further into this. I would like to take a similar approach here.
Suravee
> Thanks,
>
> tglx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-07-23 7:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 9:14 [RFCv2 PATCH 0/8] Introducing ACPI support for GICv2m Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 1/8] irqdomain: Introduce irq_domain_ops.init_alloc_info Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-20 21:28 ` Thomas Gleixner
2015-07-20 21:28 ` Thomas Gleixner
2015-07-23 6:50 ` Suravee Suthikulpanit [this message]
2015-07-23 6:50 ` Suravee Suthikulpanit
2015-07-23 6:50 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 2/8] gic: Introduce gic_init_irq_alloc_info() Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 3/8] gicv2m: Convert to use GIC irq_domain_ops.init_alloc_info Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 4/8] acpi: gsi: Adding acpi_init_irq_alloc_info() hook Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 5/8] arm64: Adding arch-specific acpi_init_irq_alloc_info Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 6/8] gic: acpi: Introduce GIC MSI frame handle and helper functions Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 7/8] gicv2m: Introducing gicv2m_acpi_init() Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` [RFCv2 PATCH 8/8] pci: acpi: Bind GICv2m MSI frame to PCI host bridge Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-13 9:14 ` Suravee Suthikulpanit
2015-07-17 15:46 ` [RFCv2 PATCH 0/8] Introducing ACPI support for GICv2m Marc Zyngier
2015-07-17 15:46 ` Marc Zyngier
2015-07-23 6:49 ` Suravee Suthikulpanit
2015-07-23 6:49 ` Suravee Suthikulpanit
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=55B08EC2.4000204@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=al.stone@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=grant.likely@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=leo.duran@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=msalter@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=sherry.hurwitz@amd.com \
--cc=tglx@linutronix.de \
--cc=tomasz.nowicki@linaro.org \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.