From: Alistair Popple <alistair@popple.id.au>
To: linuxppc-dev@lists.ozlabs.org
Cc: Alistair Popple <alistair@popple.id.au>,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
Jeremy Kerr <jk@ozlabs.org>
Subject: [PATCH 7/8] powernv/opal-dump: Convert to irq domain
Date: Thu, 2 Apr 2015 14:22:31 +1100 [thread overview]
Message-ID: <1427944952-17452-7-git-send-email-alistair@popple.id.au> (raw)
In-Reply-To: <1427944952-17452-1-git-send-email-alistair@popple.id.au>
Convert the opal dump driver to the new opal irq domain.
Signed-off-by: Alistair Popple <alistair@popple.id.au>
---
arch/powerpc/platforms/powernv/opal-dump.c | 33 +++++++++++++++---------------
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal-dump.c b/arch/powerpc/platforms/powernv/opal-dump.c
index 23260f7..812f168 100644
--- a/arch/powerpc/platforms/powernv/opal-dump.c
+++ b/arch/powerpc/platforms/powernv/opal-dump.c
@@ -15,6 +15,7 @@
#include <linux/vmalloc.h>
#include <linux/pagemap.h>
#include <linux/delay.h>
+#include <linux/interrupt.h>
#include <asm/opal.h>
@@ -60,7 +61,7 @@ static ssize_t dump_type_show(struct dump_obj *dump_obj,
struct dump_attribute *attr,
char *buf)
{
-
+
return sprintf(buf, "0x%x %s\n", dump_obj->type,
dump_type_to_string(dump_obj->type));
}
@@ -408,24 +409,16 @@ static void schedule_process_dump(void)
* Once we get notification, we add sysfs entries for it.
* We only fetch the dump on demand, and create sysfs asynchronously.
*/
-static int dump_event(struct notifier_block *nb,
- unsigned long events, void *change)
+static irqreturn_t dump_event(int irq, void *data)
{
- if (events & OPAL_EVENT_DUMP_AVAIL)
- schedule_process_dump();
+ schedule_process_dump();
- return 0;
+ return IRQ_HANDLED;
}
-static struct notifier_block dump_nb = {
- .notifier_call = dump_event,
- .next = NULL,
- .priority = 0
-};
-
void __init opal_platform_dump_init(void)
{
- int rc;
+ int rc, irq;
/* ELOG not supported by firmware */
if (!opal_check_token(OPAL_DUMP_READ))
@@ -445,10 +438,18 @@ void __init opal_platform_dump_init(void)
return;
}
- rc = opal_notifier_register(&dump_nb);
+ irq = opal_event_request(ilog2(OPAL_EVENT_DUMP_AVAIL));
+ if (!irq) {
+ pr_err("%s: Can't register OPAL event irq (%d)\n",
+ __func__, irq);
+ return;
+ }
+
+ rc = request_irq(irq, dump_event,
+ IRQ_TYPE_LEVEL_HIGH, "opal-dump", NULL);
if (rc) {
- pr_warn("%s: Can't register OPAL event notifier (%d)\n",
- __func__, rc);
+ pr_err("%s: Can't request OPAL event irq (%d)\n",
+ __func__, rc);
return;
}
--
1.8.3.2
next prev parent reply other threads:[~2015-04-02 3:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 3:22 [PATCH 1/8] powerpc/powernv: Add a virtual irqchip for opal events Alistair Popple
2015-04-02 3:22 ` [PATCH 2/8] ipmi/powernv: Convert to irq event interface Alistair Popple
2015-04-02 3:22 ` [PATCH 3/8] hvc: Convert to using interrupts instead of opal events Alistair Popple
2015-04-02 3:22 ` [PATCH 4/8] powernv/eeh: Update the EEH code to use the opal irq domain Alistair Popple
2015-04-02 3:22 ` [PATCH 5/8] powernv/opal: Convert opal message events to " Alistair Popple
2015-04-02 3:22 ` [PATCH 6/8] powernv/elog: Convert elog " Alistair Popple
2015-04-02 3:22 ` Alistair Popple [this message]
2015-04-02 3:22 ` [PATCH 8/8] opal: Remove events notifier Alistair Popple
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=1427944952-17452-7-git-send-email-alistair@popple.id.au \
--to=alistair@popple.id.au \
--cc=gwshan@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).