From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linus.walleij@linaro.org, mst@redhat.com,
virtualization@lists.linux-foundation.org,
bgolaszewski@baylibre.com, linux-riscv@lists.infradead.org,
jasowang@redhat.com
Subject: Re: [PATCH] drivers: gpio: add virtio-gpio guest driver
Date: Sun, 29 Nov 2020 23:10:50 +0100 [thread overview]
Message-ID: <20201129221050.GH456020@latitude> (raw)
In-Reply-To: <20201127183003.2849-1-info@metux.net>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Hi,
On Fri, Nov 27, 2020 at 07:30:03PM +0100, Enrico Weigelt, metux IT consult wrote:
> Introducing new gpio driver for virtual GPIO devices via virtio.
>
> The driver allows routing gpio control into VM guests, eg. brigding
> virtual gpios to specific host gpios, or attaching simulators for
> automatic application testing.
>
> Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
is there a spec of the virtio-gpio protocol available? If so, linking it
in the commit message and/or driver/Kconfig would be nice.
Best regards,
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-29 22:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 18:30 [PATCH] drivers: gpio: add virtio-gpio guest driver Enrico Weigelt, metux IT consult
2020-11-27 18:45 ` Randy Dunlap
2020-12-03 19:01 ` Enrico Weigelt, metux IT consult
2020-11-27 19:33 ` kernel test robot
2020-11-29 20:11 ` Michael S. Tsirkin
2020-11-29 22:10 ` Jonathan Neuschäfer [this message]
2020-12-03 19:12 ` Enrico Weigelt, metux IT consult
2020-12-02 14:15 ` Bartosz Golaszewski
2020-12-03 19:00 ` Enrico Weigelt, metux IT consult
2020-12-03 22:35 ` Michael Walle
2020-12-04 8:28 ` Enrico Weigelt, metux IT consult
2020-12-04 9:06 ` Michael Walle
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 17:49 Enrico Weigelt, metux IT consult
2021-06-16 8:31 ` Linus Walleij
2021-06-16 11:49 ` Viresh Kumar
2021-06-16 15:04 ` Enrico Weigelt, metux IT consult
2021-06-17 3:59 ` Viresh Kumar
2021-06-17 9:54 ` Enrico Weigelt, metux IT consult
2021-06-17 11:47 ` Viresh Kumar
2021-06-16 14:41 ` Enrico Weigelt, metux IT consult
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=20201129221050.GH456020@latitude \
--to=j.neuschaefer@gmx.net \
--cc=bgolaszewski@baylibre.com \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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