All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: virtio-comment@lists.oasis-open.org
Cc: "Vincent Guittot" <vincent.guittot@linaro.org>,
	"Bill Mills" <bill.mills@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Enrico Weigelt, metux IT consult" <info@metux.net>,
	"Bartosz Golaszewski" <bgolaszewski@baylibre.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Jason Wang" <jasowang@redhat.com>
Subject: [virtio-comment] Re: [PATCH] virtio-gpio: add the device specification
Date: Thu, 3 Jun 2021 18:16:05 +0530	[thread overview]
Message-ID: <20210603124605.zfsxatqwrefuhq2v@vireshk-i7> (raw)
In-Reply-To: <5672086c33948b7f765abb92de3f6846c8e1351f.1622724078.git.viresh.kumar@linaro.org>

On 03-06-21, 18:13, Viresh Kumar wrote:
> virtio-gpio is a virtual GPIO controller. It provides a way to flexibly
> communicate with the host GPIO controllers from the guest.
> 
> This patch adds the specification for it.
> 
> Based on the initial work done by:
> "Enrico Weigelt, metux IT consult" <lkml@metux.net>.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  conformance.tex |  26 ++++-
>  content.tex     |   1 +
>  virtio-gpio.tex | 256 ++++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 279 insertions(+), 4 deletions(-)
>  create mode 100644 virtio-gpio.tex

And here is the new issue for the same.

https://github.com/oasis-tcs/virtio-spec/issues/110

-- 
viresh

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2021-06-03 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 12:43 [virtio-comment] [PATCH] virtio-gpio: add the device specification Viresh Kumar
2021-06-03 12:46 ` Viresh Kumar [this message]
2021-06-04  8:10 ` [virtio-comment] " Viresh Kumar

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=20210603124605.zfsxatqwrefuhq2v@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=bill.mills@linaro.org \
    --cc=info@metux.net \
    --cc=jasowang@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=vincent.guittot@linaro.org \
    --cc=virtio-comment@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.