From: Jonas Bonn <jonas@southpole.se>
To: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
linux-kernel@vger.kernel.org, linux@openrisc.net
Subject: Re: [PATCH] openrisc: irq: use irqchip framework
Date: Mon, 19 May 2014 16:44:57 +0200 [thread overview]
Message-ID: <537A18E9.4010301@southpole.se> (raw)
In-Reply-To: <1400502328-23974-1-git-send-email-stefan.kristiansson@saunalahti.fi>
Hi Stefan,
This looks good. Let's complete the the cleanup of this driver while
we're at it:
i) Move this file to drivers/irqchip/
ii) Put a Depends on CONFIG_ARCH_OPENRISC in the Kconfig
iii) Provide documentation for the binding at
Documentation/devicetree/bindings/interrupt-controller/
Copy final result to Thomas Gleixner who maintains the irqchip bits.
Thanks,
Jonas
On 05/19/2014 02:25 PM, Stefan Kristiansson wrote:
> In addition to consolidating the or1k-pic initialization with
> how other interrupt controllers are initialized, this makes
> OpenRISC less tied to its on-cpu interrupt controller.
>
> Signed-off-by: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> ---
> arch/openrisc/kernel/irq.c | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
> diff --git a/arch/openrisc/kernel/irq.c b/arch/openrisc/kernel/irq.c
> index 8ec77bc..f6f4683 100644
> --- a/arch/openrisc/kernel/irq.c
> +++ b/arch/openrisc/kernel/irq.c
> @@ -19,10 +19,13 @@
> #include <linux/of.h>
> #include <linux/ftrace.h>
Do we really need to pull in ftrace.h?
<snip>
This last bit (below) stays in the arch/openrisc directory.
> void __init init_IRQ(void)
> {
> - or1k_irq_init();
> + irqchip_init();
> }
>
> void __irq_entry do_IRQ(struct pt_regs *regs)
>
next prev parent reply other threads:[~2014-05-19 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 12:25 [PATCH] openrisc: irq: use irqchip framework Stefan Kristiansson
2014-05-19 14:44 ` Jonas Bonn [this message]
2014-05-19 19:54 ` Stefan Kristiansson
2014-05-20 6:45 ` Jonas Bonn
2014-05-21 5:31 ` Stefan Kristiansson
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=537A18E9.4010301@southpole.se \
--to=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@openrisc.net \
--cc=stefan.kristiansson@saunalahti.fi \
/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