From: Peng Hao <peng.hao2@zte.com.cn>
To: robh+dt@kernel.org, mark.rutland@arm.com, arnd@arndb.de,
gregkh@linuxfoundation.org, andy@infradead.org,
dvhart@infradead.org
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, hutao@cn.fujitsu.com,
Peng Hao <peng.hao2@zte.com.cn>
Subject: [PATCH V2 2/4] misc/pvpanic: add MMIO support
Date: Thu, 25 Oct 2018 01:12:14 +0800 [thread overview]
Message-ID: <1540401136-78500-2-git-send-email-peng.hao2@zte.com.cn> (raw)
In-Reply-To: <1540401136-78500-1-git-send-email-peng.hao2@zte.com.cn>
On some architectures (e.g. arm64), it's preferable to use MMIO, since
this can be used standalone. Add MMIO support to the pvpanic driver.
Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
---
drivers/misc/pvpanic.c | 18 ++++++++++++++++--
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index fd86dab..bcfefdd 100644
--- a/drivers/misc/pvpanic.c
+++ b/drivers/misc/pvpanic.c
@@ -43,6 +43,8 @@
static u16 port;
+static void __iomem *base;
+
static struct acpi_driver pvpanic_driver = {
.name = "pvpanic",
.class = "QEMU",
@@ -57,7 +59,10 @@
static void
pvpanic_send_event(unsigned int event)
{
- outb(event, port);
+ if (port)
+ outb(event, port);
+ else if (base)
+ writeb(event, base);
}
static int
@@ -77,6 +82,8 @@
static acpi_status
pvpanic_walk_resources(struct acpi_resource *res, void *context)
{
+ struct acpi_resource_fixed_memory32 *fixmem32;
+
switch (res->type) {
case ACPI_RESOURCE_TYPE_END_TAG:
return AE_OK;
@@ -85,6 +92,11 @@
port = res->data.io.minimum;
return AE_OK;
+ case ACPI_RESOURCE_TYPE_FIXED_MEMORY32:
+ fixmem32 = &res->data.fixed_memory32;
+ base = ioremap(fixmem32->address, fixmem32->address_length);
+ return AE_OK;
+
default:
return AE_ERROR;
}
@@ -104,7 +116,7 @@ static int pvpanic_add(struct acpi_device *device)
acpi_walk_resources(device->handle, METHOD_NAME__CRS,
pvpanic_walk_resources, NULL);
- if (!port)
+ if (!port && !base)
return -ENODEV;
atomic_notifier_chain_register(&panic_notifier_list,
@@ -118,6 +130,8 @@ static int pvpanic_remove(struct acpi_device *device)
atomic_notifier_chain_unregister(&panic_notifier_list,
&pvpanic_panic_nb);
+ if (base)
+ iounmap(base);
return 0;
}
--
1.8.3.1
next prev parent reply other threads:[~2018-10-24 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 17:12 [PATCH V2 1/4] misc/pvpanic: move pvpanic to misc as common driver Peng Hao
2018-10-24 13:08 ` Andy Shevchenko
2018-10-24 17:12 ` Peng Hao [this message]
2018-10-24 13:09 ` [PATCH V2 2/4] misc/pvpanic: add MMIO support Andy Shevchenko
[not found] ` <201810261140543493998@zte.com.cn>
2018-10-26 7:11 ` Arnd Bergmann
2018-10-24 17:12 ` [PATCH V2 3/4] misc/pvpanic: add support to pvpanic device information by using FDT Peng Hao
2018-10-24 13:12 ` Andy Shevchenko
2018-10-24 17:12 ` [PATCH V2 4/4] misc/pvpanic : pvpanic: add document for pvpanic-mmio DT Peng Hao
2018-10-24 13:35 ` Rob Herring
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=1540401136-78500-2-git-send-email-peng.hao2@zte.com.cn \
--to=peng.hao2@zte.com.cn \
--cc=andy@infradead.org \
--cc=arnd@arndb.de \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hutao@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).