All of lore.kernel.org
 help / color / mirror / Atom feed
From: jay.aurabind@gmail.com (Jay Aurabind)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Registering shared & unshared interrupt handlers
Date: Mon, 17 Feb 2014 12:06:58 +0530	[thread overview]
Message-ID: <5301AE0A.5080004@gmail.com> (raw)

Dear all,

I've been going through Robert Love's LKD. Here is an excerpt from it
regarding registration of interrupt handlers:

"When request_irq() is called with IRQF_SHARED specified, the call
succeeds only if the interrupt line is currently not registered, or if
all registered handlers on the line also specified IRQF_SHARED. Shared
handlers, however, can mix usage of IRQF_DISABLED."

As far as I understand, the first sentence tells that a line currently
having shared handlers *will only have* handlers registered with
IRQF_SHARED flag in the past. Correct ?

If a interrupt line has been registered by a handler specified as non
shared, then whats the point in allowing a new handler with a "shared"
flag registering to the same line ? So how does the mixing of shared and
unshared interrupt handlers for the same line go together as mentioned
by the 2nd sentence ?

Or does it mean that a shared handler which already succeeded the
registration can further register a non shared and shared interrupt
handlers? ( That doesnt make sense, but still... )  ? Simply put, can
someone please elaborate on the second sentence I quoted from the book ?


Thanks and Regards,
Aurabindo J
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140217/08f58b8d/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 291 bytes
Desc: OpenPGP digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140217/08f58b8d/attachment.bin 

             reply	other threads:[~2014-02-17  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17  6:36 Jay Aurabind [this message]
2014-02-17  6:55 ` Registering shared & unshared interrupt handlers Jay Aurabind
2014-02-17  7:34 ` anish singh

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=5301AE0A.5080004@gmail.com \
    --to=jay.aurabind@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.