mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Singaravelan Nallasellan" <singaravelann@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Acceptable Interrupt Latency in Linux kernel
Date: Thu, 25 Sep 2008 14:12:50 -0700	[thread overview]
Message-ID: <3baf3d760809251412l28423a22lba5b1b57c411c87e@mail.gmail.com> (raw)

What is the tolerable interrupt latency for the Linux interrupt handler?

I need to write a driver which will require to invoke a function from
other driver
to read the hardware register. That function will send a message to
the firmware in the some other hardware.

The firmware will go into a bus to read the register and return the
value. This firmware generates an interrupt of the completion of the
register read.

So the whole process of register read will take time to know the
interrupt source.

Currently I dont have the exact duration to read a single register. I
am also planning to push the register read to work queue and return
with IRQ handled from the ISR without knowing the hardware
status.There is a potential to mis handle the interrupt.

If I know the acceptable interrupt latency, It will simplify the ISR handling.

Thanks

                 reply	other threads:[~2008-09-25 21:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3baf3d760809251412l28423a22lba5b1b57c411c87e@mail.gmail.com \
    --to=singaravelann@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®