From: Mukesh Ojha <mukesh02@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, jk@ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/powernv/opal-dump : Use IRQ_HANDLED instead of numbers in interrupt handler
Date: Wed, 15 Feb 2017 15:57:38 +0530 [thread overview]
Message-ID: <62c1a1c3-3a9e-2a9b-b7c1-c23d8d6efcb6@linux.vnet.ibm.com> (raw)
In-Reply-To: <f87a41d5-9647-67c4-735e-a7df86c4ff3a@ozlabs.org>
Hi Jeremy,
On Wednesday 15 February 2017 08:48 AM, Jeremy Kerr wrote:
> Hi Mukesh,
>
>> Converts all the return explicit number to a more proper IRQ_HANDLED,
>> which looks proper incase of interrupt handler returning case.
> This looks good to me, but can you describe the effects of those changes
> to the interrupt handler's return code? ie, what happened in the
> erroneous case where we returned 0 (== IRQ_NONE) - does this fix a
> user-visible issue?
>
> Cheers,
The return value of an interrupt handler is the special type
irqreturn_t. An interrupt handler can return two special values,
IRQ_NONE or IRQ_HANDLED. The former is returned when the interrupt
handler detects an interrupt for which its device was not
the originator. The latter is returned if the interrupt handler was
correctly invoked, and its device did indeed cause the interrupt.
No, this is not user visible issue..and also here it does not matter
what we return from here as we
are not handling the return value of the handler. This handler gets
triggered when we get interrupt
from opal and in handler we do a opal call which on successful scenario
disable the interrupt bit which
was set.
-Mukesh
>
>
> Jeremy
>
next prev parent reply other threads:[~2017-02-15 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 9:08 [PATCH 1/2] powerpc/powernv/opal-dump : Handles opal_dump_info properly Mukesh Ojha
2016-12-01 9:08 ` [PATCH 2/2] powerpc/powernv/opal-dump : Use IRQ_HANDLED instead of numbers in interrupt handler Mukesh Ojha
2017-02-15 3:18 ` Jeremy Kerr
2017-02-15 10:27 ` Mukesh Ojha [this message]
2017-02-16 2:40 ` Jeremy Kerr
2017-02-20 13:19 ` Mukesh Ojha
2017-02-27 0:16 ` Jeremy Kerr
2017-02-15 5:08 ` Stewart Smith
2017-02-15 6:18 ` Mukesh Ojha
2016-12-06 6:37 ` [PATCH 1/2] powerpc/powernv/opal-dump : Handles opal_dump_info properly Mukesh Ojha
2017-02-13 6:32 ` Mukesh Ojha
2017-02-15 3:18 ` Jeremy Kerr
2017-02-15 5:04 ` Stewart Smith
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=62c1a1c3-3a9e-2a9b-b7c1-c23d8d6efcb6@linux.vnet.ibm.com \
--to=mukesh02@linux.vnet.ibm.com \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).