From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
bgolaszewski@baylibre.com, "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Linux Documentation <linux-doc@vger.kernel.org>,
linux-gpio@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver
Date: Mon, 24 May 2021 16:57:03 +0530 [thread overview]
Message-ID: <CAOh2x=kcM351ObubnQSzUa=FVBQUmAUhz4u8ExORUthQQ0WbGQ@mail.gmail.com> (raw)
In-Reply-To: <20201203191135.21576-2-info@metux.net>
On Fri, Dec 4, 2020 at 12:51 AM Enrico Weigelt, metux IT consult
<info@metux.net> 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.
>
> Changes v2:
> * fixed uapi header license
> * sorted include's
> * fixed formatting
> * fixed unneeded devm allocation - plain kzalloc/kfree is enough
> * fixed missing devm_kzalloc fail check
> * use devm_kcalloc() for array allocation
> * added virtio-gpio protocol specification
Hi Enrico,
We (Linaro's Project Stratos
https://linaro.atlassian.net/wiki/spaces/STR/overview)
are interested in this stuff. I was trying to look at the last status
of all this. Few
questions for you:
- Was the spec ever posted to virtio-dev list ? I thought that's the
very first step before
we merge the code.
- Any follow up on this patchset ?
Thanks. I will be happy to help otherwise and have cycles to work on
this if you need my help.
--
viresh
next prev parent reply other threads:[~2021-05-24 11:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 19:11 [PATCH v2 1/2] drivers: gpio: put virtual gpio device into their own submenu Enrico Weigelt, metux IT consult
2020-12-03 19:11 ` [PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver Enrico Weigelt, metux IT consult
2020-12-04 3:35 ` Jason Wang
2020-12-04 9:36 ` Enrico Weigelt, metux IT consult
2020-12-07 3:48 ` Jason Wang
2020-12-07 9:33 ` Enrico Weigelt, metux IT consult
2020-12-08 2:49 ` Jason Wang
2021-04-13 11:07 ` Alex Bennée
2020-12-05 7:59 ` Enrico Weigelt, metux IT consult
2020-12-05 19:32 ` Michael S. Tsirkin
2020-12-05 20:05 ` Enrico Weigelt, metux IT consult
2020-12-07 3:16 ` Jason Wang
2020-12-07 13:52 ` Michael S. Tsirkin
2020-12-07 20:34 ` Enrico Weigelt, metux IT consult
2020-12-07 3:12 ` Jason Wang
2020-12-07 13:53 ` Michael S. Tsirkin
2020-12-08 2:36 ` Jason Wang
2020-12-08 7:02 ` Enrico Weigelt, metux IT consult
2020-12-09 9:31 ` Jason Wang
2020-12-09 10:33 ` Enrico Weigelt, metux IT consult
2020-12-08 10:10 ` Michal Suchánek
2020-12-08 12:33 ` Enrico Weigelt, metux IT consult
2020-12-09 10:34 ` Michal Suchánek
2020-12-05 20:15 ` Howto listen to/handle gpio state changes ? " Enrico Weigelt, metux IT consult
2020-12-08 9:38 ` Linus Walleij
2020-12-08 14:04 ` Enrico Weigelt, metux IT consult
2020-12-08 16:15 ` Grygorii Strashko
2020-12-09 8:51 ` Linus Walleij
2020-12-09 11:19 ` Arnd Bergmann
2020-12-09 12:53 ` Linus Walleij
2020-12-09 20:22 ` Grygorii Strashko
2020-12-09 20:38 ` Arnd Bergmann
2020-12-10 13:32 ` Grygorii Strashko
2021-05-24 11:27 ` Viresh Kumar [this message]
2021-05-25 12:59 ` Enrico Weigelt, metux IT consult
2021-05-26 3:32 ` Viresh Kumar
2021-07-03 8:05 ` Michael S. Tsirkin
2021-07-05 3:51 ` Viresh Kumar
2020-12-07 9:55 ` [PATCH v2 1/2] drivers: gpio: put virtual gpio device into their own submenu Andy Shevchenko
2020-12-07 10:31 ` Bartosz Golaszewski
2020-12-07 11:22 ` 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='CAOh2x=kcM351ObubnQSzUa=FVBQUmAUhz4u8ExORUthQQ0WbGQ@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=corbet@lwn.net \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mst@redhat.com \
--cc=vincent.guittot@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).