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 v3 0/2] vfio: platform: Improve reset support
Date: Wed, 11 Apr 2018 11:15:47 +0200 [thread overview]
Message-ID: <1523438149-16433-2-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1523438149-16433-1-git-send-email-geert+renesas@glider.be>
Hi all,
This patch series improves reset support for vfio-platform:
- The first patch fixes a bug I ran into while working on this.
- The second patch implements generic DT reset controller support, for
devices that are connected to an SoC-internal reset controller and
can be reset in a generic way. This avoids having to write/change a
vfio-specific reset driver for each and every device to be
passed-through to a guest.
Changes compared to v2:
- Add Reviewed-by,
- Merge similar checks in vfio_platform_has_reset().
Changes compared to v1:
- Add Reviewed-by,
- Don't store error values in vdev->reset_control,
- Use of_reset_control_get_exclusive() instead of
__of_reset_control_get(),
- Improve description.
This has been tested on R-Car H3/Salvator-XS by exporting a GPIO module
to a QEMU+KWM guest: the GPIO module is reset before QEMU opens the vfio
device, and reset again after QEMU has released it, as can be witnessed
by the LEDs connected to the GPIOs.
Thanks!
Geert Uytterhoeven (2):
vfio: platform: Fix reset module leak in error path
vfio: platform: Add generic DT reset support
drivers/vfio/platform/vfio_platform_common.c | 35 +++++++++++++++++++++------
drivers/vfio/platform/vfio_platform_private.h | 1 +
2 files changed, 29 insertions(+), 7 deletions(-)
--
2.7.4
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-04-11 9:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 9:15 [PATCH] vfio: platform: Fix using devices in PM Domains Geert Uytterhoeven
2018-04-11 9:15 ` Geert Uytterhoeven [this message]
2018-04-11 9:15 ` [PATCH v3 1/2] vfio: platform: Fix reset module leak in error path Geert Uytterhoeven
2018-04-13 8:55 ` Auger Eric
2018-05-11 19:45 ` Alex Williamson
2018-04-11 9:15 ` [PATCH v3 2/2] vfio: platform: Add generic DT reset support Geert Uytterhoeven
2018-04-12 7:00 ` Simon Horman
2018-04-12 10:31 ` Auger Eric
2018-04-12 11:32 ` Geert Uytterhoeven
2018-04-12 11:49 ` Auger Eric
2018-04-12 12:36 ` Sinan Kaya
2018-04-12 13:12 ` Geert Uytterhoeven
2018-04-12 14:10 ` Philipp Zabel
2018-04-12 16:02 ` Geert Uytterhoeven
2018-04-13 8:52 ` Auger Eric
2018-04-13 9:02 ` Geert Uytterhoeven
2018-04-13 9:22 ` Philipp Zabel
2018-04-13 10:05 ` Auger Eric
2018-04-13 11:56 ` Geert Uytterhoeven
2018-04-11 9:21 ` [PATCH] vfio: platform: Fix using devices in PM Domains Geert Uytterhoeven
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=1523438149-16433-2-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).