From: Shawn Guo <shawn.guo@linaro.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
Russell King <linux@arm.linux.org.uk>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mxs: icoll: Add function to register an interrupt as FIQ source
Date: Thu, 2 May 2013 10:39:00 +0800 [thread overview]
Message-ID: <20130502023858.GD3442@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1367243917-5177-1-git-send-email-maxime.ripard@free-electrons.com>
On Mon, Apr 29, 2013 at 03:58:37PM +0200, Maxime Ripard wrote:
> MXS, unlike other ARM platforms,
How are other ARM platforms handling that?
> has no way to make a FIQ from an
> interrupt from a driver, without poking directly into the icoll.
>
> Add an exported function to do this.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
> arch/arm/mach-mxs/icoll.c | 11 +++++++++++
This will become drivers/irqchip/irq-mxs.c after the merge window.
Shawn
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/arm/mach-mxs/icoll.c b/arch/arm/mach-mxs/icoll.c
> index 8fb23af..1bb16da 100644
> --- a/arch/arm/mach-mxs/icoll.c
> +++ b/arch/arm/mach-mxs/icoll.c
> @@ -16,6 +16,7 @@
> * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
> */
>
> +#include <linux/export.h>
> #include <linux/kernel.h>
> #include <linux/init.h>
> #include <linux/irq.h>
> @@ -34,6 +35,7 @@
> #define HW_ICOLL_INTERRUPTn_SET(n) (0x0124 + (n) * 0x10)
> #define HW_ICOLL_INTERRUPTn_CLR(n) (0x0128 + (n) * 0x10)
> #define BM_ICOLL_INTERRUPTn_ENABLE 0x00000004
> +#define BM_ICOLL_INTERRUPTn_FIQ_ENABLE 0x00000010
> #define BV_ICOLL_LEVELACK_IRQLEVELACK__LEVEL0 0x1
>
> #define ICOLL_NUM_IRQS 128
> @@ -41,6 +43,15 @@
> static void __iomem *icoll_base = MXS_IO_ADDRESS(MXS_ICOLL_BASE_ADDR);
> static struct irq_domain *icoll_domain;
>
> +void mxs_icoll_set_irq_fiq(unsigned int irq)
> +{
> + struct irq_data *d = irq_get_irq_data(irq);
> +
> + __raw_writel(BM_ICOLL_INTERRUPTn_FIQ_ENABLE,
> + icoll_base + HW_ICOLL_INTERRUPTn_SET(d->hwirq));
> +}
> +EXPORT_SYMBOL(mxs_icoll_set_irq_fiq);
> +
> static void icoll_ack_irq(struct irq_data *d)
> {
> /*
> --
> 1.8.1.2
>
next prev parent reply other threads:[~2013-05-02 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 13:58 Maxime Ripard
2013-05-02 2:39 ` Shawn Guo [this message]
2013-05-02 8:35 ` Maxime Ripard
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=20130502023858.GD3442@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maxime.ripard@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®