From: Jiang Liu <jiang.liu@linux.intel.com>
To: Qais Yousef <qais.yousef@imgtec.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Cc: marc.zyngier@arm.com, jason@lakedaemon.net, linux-mips@linux-mips.org
Subject: Re: [PATCH 2/6] irqdomain: add a new send_ipi() to irq_domain_ops
Date: Thu, 24 Sep 2015 00:44:35 +0800 [thread overview]
Message-ID: <5602D6F3.7030709@linux.intel.com> (raw)
In-Reply-To: <1443019758-20620-3-git-send-email-qais.yousef@imgtec.com>
On 2015/9/23 22:49, Qais Yousef wrote:
> For generic ipi core to use. It takes hwirq as its sole argument.
> Hopefully this is generic enough? Should we pass something more abstract?
>
> Signed-off-by: Qais Yousef <qais.yousef@imgtec.com>
> ---
> include/linux/irqdomain.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/irqdomain.h b/include/linux/irqdomain.h
> index 9b3dc6c2a3cc..cef9e6158be0 100644
> --- a/include/linux/irqdomain.h
> +++ b/include/linux/irqdomain.h
> @@ -92,6 +92,7 @@ struct irq_domain_ops {
> void (*activate)(struct irq_domain *d, struct irq_data *irq_data);
> void (*deactivate)(struct irq_domain *d, struct irq_data *irq_data);
> #endif
> + void (*send_ipi)(irq_hw_number_t hwirq);
Hi Qais,
Instead of extending the irq_domain_ops, how about extending
irq_chip instead? If we treat IPI as a sort of irq controller, and
irq_chip is used to encapsulate all irq controller related operations,
and irq_domain_ops is mainly used to allocated resources instead of
operating corresponding hardware.
Thanks!
Gerry
> };
>
> extern struct irq_domain_ops irq_generic_chip_ops;
>
next prev parent reply other threads:[~2015-09-23 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 14:49 [PATCH 0/6] Implement generic IPI support mechanism Qais Yousef
2015-09-23 14:49 ` [PATCH 1/6] irqdomain: add new IRQ_DOMAIN_FLAGS_IPI Qais Yousef
2015-09-23 14:49 ` [PATCH 2/6] irqdomain: add a new send_ipi() to irq_domain_ops Qais Yousef
2015-09-23 16:44 ` Jiang Liu [this message]
2015-09-24 8:12 ` Qais Yousef
2015-09-23 14:49 ` [PATCH 3/6] irqdomain: add struct irq_hwcfg and helper functions Qais Yousef
2015-09-23 14:49 ` [PATCH 4/6] irq: add a new generic IPI handling code to irq core Qais Yousef
2015-09-23 16:50 ` Jiang Liu
2015-09-24 8:26 ` Qais Yousef
2015-09-29 16:15 ` Thomas Gleixner
2015-09-23 14:49 ` [PATCH 5/6] irqchip: mips-gic: add a IPI hierarchy domain Qais Yousef
2015-09-23 14:49 ` [PATCH 6/6] irqchip: mips-gic: use the new generic IPI API Qais Yousef
2015-09-23 16:54 ` [PATCH 0/6] Implement generic IPI support mechanism Jiang Liu
2015-09-24 8:39 ` Qais Yousef
2015-09-29 20:48 ` Thomas Gleixner
2015-09-30 13:34 ` Qais Yousef
2015-09-30 14:03 ` Thomas Gleixner
2015-09-30 14:08 ` Qais Yousef
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=5602D6F3.7030709@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=marc.zyngier@arm.com \
--cc=qais.yousef@imgtec.com \
--cc=tglx@linutronix.de \
/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