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 2/4] pvpanic: add pvpanic support for arm64
Date: Wed, 24 Oct 2018 01:25:35 +0800 [thread overview]
Message-ID: <1540315537-70007-2-git-send-email-peng.hao2@zte.com.cn> (raw)
In-Reply-To: <1540315537-70007-1-git-send-email-peng.hao2@zte.com.cn>
pvpanic device is a qemu-specific emulation device. Pvpanic
devices are now available for ARM64. This patch supports the APCI
way to get device information.
Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
---
drivers/misc/pvpanic.c | 22 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index fd86dab..bdcff8b 100644
--- a/drivers/misc/pvpanic.c
+++ b/drivers/misc/pvpanic.c
@@ -35,13 +35,16 @@
static const struct acpi_device_id pvpanic_device_ids[] = {
{ "QEMU0001", 0 },
+ { "PVPANIC01", 0 },
{ "", 0 },
};
MODULE_DEVICE_TABLE(acpi, pvpanic_device_ids);
#define PVPANIC_PANICKED (1 << 0)
+
+static void __iomem *base;
static struct acpi_driver pvpanic_driver = {
.name = "pvpanic",
@@ -57,7 +60,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 +83,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;
@@ -84,7 +92,11 @@
case ACPI_RESOURCE_TYPE_IO:
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-23 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 17:25 [PATCH 1/4] pvpanic: move pvpanic to misc as common driver Peng Hao
2018-10-23 17:25 ` Peng Hao [this message]
2018-10-23 10:38 ` [PATCH 2/4] pvpanic: add pvpanic support for arm64 Mark Rutland
2018-10-23 17:25 ` [PATCH 3/4] pvpanic: add access to pvpanic device information by using FDT Peng Hao
2018-10-23 17:25 ` [PATCH 4/4] pvpanic: add document for pvpanic-mmio DT Peng Hao
2018-10-23 10:41 ` Mark Rutland
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=1540315537-70007-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).