From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Baptiste Reynal <b.reynal@virtualopensystems.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
kvm@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 2/2] vfio: platform: Add generic DT reset controller support
Date: Tue, 10 Apr 2018 17:53:47 +0200 [thread overview]
Message-ID: <1523375627-23746-3-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1523375627-23746-1-git-send-email-geert+renesas@glider.be>
Vfio-platform requires reset support, provided either by ACPI, or, on DT
platforms, by a device-specific reset driver matching against the
device's compatible value.
On many SoCs, devices are connected to an SoC-internal reset controller.
If the reset hierarchy is described in DT using "resets" properties,
such devices can be reset in a generic way through the reset controller
subsystem. Hence add support for this, avoiding the need to write
device-specific reset drivers for each single device on affected SoCs.
Devices that do require a more complex reset procedure can still provide
a device-specific reset driver, as that takes precedence.
Note that this functionality depends on CONFIG_RESET_CONTROLLER=y, and
becomes a no-op (as in: "No reset function found for device") if reset
controller support is disabled.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
v2:
- Don't store error values in vdev->reset_control,
- Use of_reset_control_get_exclusive() instead of
__of_reset_control_get(),
- Improve description.
---
drivers/vfio/platform/vfio_platform_common.c | 26 ++++++++++++++++++++++++--
drivers/vfio/platform/vfio_platform_private.h | 1 +
2 files changed, 25 insertions(+), 2 deletions(-)
diff --git a/drivers/vfio/platform/vfio_platform_common.c b/drivers/vfio/platform/vfio_platform_common.c
index b60bb5326668498c..3c13327b2777f8ec 100644
--- a/drivers/vfio/platform/vfio_platform_common.c
+++ b/drivers/vfio/platform/vfio_platform_common.c
@@ -17,6 +17,7 @@
#include <linux/iommu.h>
#include <linux/module.h>
#include <linux/mutex.h>
+#include <linux/reset.h>
#include <linux/slab.h>
#include <linux/types.h>
#include <linux/uaccess.h>
@@ -112,11 +113,19 @@ static bool vfio_platform_has_reset(struct vfio_platform_device *vdev)
if (VFIO_PLATFORM_IS_ACPI(vdev))
return vfio_platform_acpi_has_reset(vdev);
- return vdev->of_reset ? true : false;
+ if (vdev->of_reset)
+ return true;
+
+ if (vdev->reset_control)
+ return true;
+
+ return false;
}
static int vfio_platform_get_reset(struct vfio_platform_device *vdev)
{
+ struct reset_control *rstc;
+
if (VFIO_PLATFORM_IS_ACPI(vdev))
return vfio_platform_acpi_has_reset(vdev) ? 0 : -ENOENT;
@@ -127,8 +136,16 @@ static int vfio_platform_get_reset(struct vfio_platform_device *vdev)
vdev->of_reset = vfio_platform_lookup_reset(vdev->compat,
&vdev->reset_module);
}
+ if (vdev->of_reset)
+ return 0;
+
+ rstc = of_reset_control_get_exclusive(vdev->device->of_node, NULL);
+ if (!IS_ERR(rstc)) {
+ vdev->reset_control = rstc;
+ return 0;
+ }
- return vdev->of_reset ? 0 : -ENOENT;
+ return PTR_ERR(rstc);
}
static void vfio_platform_put_reset(struct vfio_platform_device *vdev)
@@ -138,6 +155,8 @@ static void vfio_platform_put_reset(struct vfio_platform_device *vdev)
if (vdev->of_reset)
module_put(vdev->reset_module);
+
+ reset_control_put(vdev->reset_control);
}
static int vfio_platform_regions_init(struct vfio_platform_device *vdev)
@@ -217,6 +236,9 @@ static int vfio_platform_call_reset(struct vfio_platform_device *vdev,
} else if (vdev->of_reset) {
dev_info(vdev->device, "reset\n");
return vdev->of_reset(vdev);
+ } else if (vdev->reset_control) {
+ dev_info(vdev->device, "reset\n");
+ return reset_control_reset(vdev->reset_control);
}
dev_warn(vdev->device, "no reset function found!\n");
diff --git a/drivers/vfio/platform/vfio_platform_private.h b/drivers/vfio/platform/vfio_platform_private.h
index 85ffe5d9d1abd94e..a56e80ae5986540b 100644
--- a/drivers/vfio/platform/vfio_platform_private.h
+++ b/drivers/vfio/platform/vfio_platform_private.h
@@ -60,6 +60,7 @@ struct vfio_platform_device {
const char *compat;
const char *acpihid;
struct module *reset_module;
+ struct reset_control *reset_control;
struct device *device;
/*
--
2.7.4
next prev parent reply other threads:[~2018-04-10 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 15:53 [PATCH v2 0/2] vfio: platform: Improve reset support Geert Uytterhoeven
2018-04-10 15:53 ` [PATCH v2 1/2] vfio: platform: Fix reset module leak in error path Geert Uytterhoeven
2018-04-11 8:09 ` Simon Horman
2018-04-10 15:53 ` Geert Uytterhoeven [this message]
2018-04-11 8:22 ` [PATCH v2 2/2] vfio: platform: Add generic DT reset controller support Philipp Zabel
2018-04-11 8:43 ` Geert Uytterhoeven
2018-04-11 8:22 ` Simon Horman
2018-04-11 8:39 ` Geert Uytterhoeven
2018-04-12 6:54 ` Simon Horman
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=1523375627-23746-3-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=devicetree@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--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).