From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Julian Fuchs <julian@fuchs.cc>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Problem with interrupt handler
Date: Mon, 25 Jan 2010 20:31:04 +0100 [thread overview]
Message-ID: <20100125193104.GC14834@pengutronix.de> (raw)
In-Reply-To: <e97c14da1001250916u9b20444k2bdb550211aca1ea@mail.gmail.com>
On Mon, Jan 25, 2010 at 06:16:08PM +0100, Julian Fuchs wrote:
> being aware of the risk to bother some people here I would
> nevertheless really appreciate your help with the following issue:
>
> Is there any difference in the request_irq() function call in
> comparison to the one in the normal kernel?
>
> I'm trying to run
>
> request_irq(irq, interrupt_handler, IRQF_SHARED | IRQF_DISABLED |
> IRQF_NODELAY, MODULE_IDENT, &stage)
>
> on 2.6.31.6-rt19 but it doesn't call interrupt_handler() when an
> interrupt is received.
>
> In the plain kernel 2.6.31 it works with this call:
>
> request_irq(irq, interrupt_handler, IRQF_SHARED | IRQF_DISABLED,
> MODULE_IDENT, &stage)
Did you try with IRQF_NODELAY on vanilla and without it in rt? Are you
sure the irq fires in rt? Does your interrupt appear in
/proc/interrupts? What platform are you working on? Do you can send
the code of a minimal example?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" 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:[~2010-01-25 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 17:16 Problem with interrupt handler Julian Fuchs
2010-01-25 19:31 ` Uwe Kleine-König [this message]
2010-01-25 22:41 ` Julian Fuchs
2010-01-26 11:00 ` Uwe Kleine-König
2010-01-25 19:35 ` Thomas Gleixner
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=20100125193104.GC14834@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=julian@fuchs.cc \
--cc=linux-rt-users@vger.kernel.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