linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Michael Haberler <ml1234@mah.priv.at>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	Jon Elson <elson@pico-systems.com>
Subject: Re: synchronize RT thread to external IRQ - suggestions?
Date: Sat, 7 Sep 2013 20:53:49 -0400	[thread overview]
Message-ID: <20130907205349.2feeef7f@gandalf.local.home> (raw)
In-Reply-To: <C5F241C8-47AB-4EA5-83D2-C067EA7F3E7B@mah.priv.at>

On Sun, 1 Sep 2013 19:40:14 +0200
Michael Haberler <ml1234@mah.priv.at> wrote:

> I've hardware at hand which would best be serviced by an RT-hardened thread after the hardware interrupts the host - in the simplest form it could be say a parport IRQ

request_threaded_irq() in the driver.

Then just set the priority of that thread to whatever you like it to be.

Or is this a user task thread?

-- Steve

      reply	other threads:[~2013-09-08  0:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01 17:40 synchronize RT thread to external IRQ - suggestions? Michael Haberler
2013-09-08  0:53 ` Steven Rostedt [this message]

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=20130907205349.2feeef7f@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=elson@pico-systems.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=ml1234@mah.priv.at \
    /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;
as well as URLs for NNTP newsgroup(s).