From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S5P: Can handle edge interrupt handler
Date: Fri, 10 Feb 2012 21:01:48 +0100 [thread overview]
Message-ID: <1683433.XtZk95zyY3@flatron> (raw)
In-Reply-To: <017401cce7f4$4623f5a0$d26be0e0$@samsung.com>
I wonder if same thing wouldn't be also needed for s3c64xx.
Also please see my comments inline.
On Friday 10 of February 2012 22:02:42 Huisung Kang wrote:
> From: KeyYoung Park <keyyoung.park@samsung.com>
>
> While wake up, if external interrupt uses handle_level_irq
> as handle_irq (it actually uses edge type irq), That interrupt is missed.
> So, if external uses edge type irq, it should use handle_edge_irq.
>
> Signed-off-by: KeyYoung Park <keyyoung.park@samsung.com>
> Signed-off-by: Huisung Kang <hs1218.kang@samsung.com>
> ---
> arch/arm/plat-s5p/irq-eint.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/plat-s5p/irq-eint.c b/arch/arm/plat-s5p/irq-eint.c
> index c496b35..6ed395e 100644
> --- a/arch/arm/plat-s5p/irq-eint.c
> +++ b/arch/arm/plat-s5p/irq-eint.c
> @@ -65,6 +65,7 @@ static int s5p_irq_eint_set_type(struct irq_data *data,
> unsigned int type) int shift;
> u32 ctrl, mask;
> u32 newvalue = 0;
> + struct irq_desc *desc = irq_to_desc(data->irq);
>
> switch (type) {
> case IRQ_TYPE_EDGE_RISING:
> @@ -115,6 +116,11 @@ static int s5p_irq_eint_set_type(struct irq_data
> *data, unsigned int type) else
> printk(KERN_ERR "No such irq number %d", offs);
>
> + if (type & IRQ_TYPE_EDGE_BOTH)
> + desc->handle_irq = handle_edge_irq;
> + else
> + desc->handle_irq = handle_level_irq;
Maybe it would be better to use __irq_set_handler_locked here instead of
touching irq_desc directly?
> +
> return 0;
> }
Regards,
Tom
next prev parent reply other threads:[~2012-02-10 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 13:02 [PATCH] ARM: S5P: Can handle edge interrupt handler Huisung Kang
2012-02-10 20:01 ` Tomasz Figa [this message]
2012-02-11 2:44 ` Huisung Kang
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=1683433.XtZk95zyY3@flatron \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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