All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jie Deng <jie.deng@intel.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	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>
Subject: Re: [virtio-comment] Re: [PATCH] Reserve device id for GPIO device
Date: Fri, 4 Jun 2021 10:28:22 +0800	[thread overview]
Message-ID: <e0bb902f-d009-8aa1-0c71-25989d3d1269@intel.com> (raw)
In-Reply-To: <0f36102a-8ce0-8cda-cb3f-3b41b346fad9@metux.net>


On 2021/6/2 19:57, Enrico Weigelt, metux IT consult wrote:
> On 02.06.21 08:42, Viresh Kumar wrote:
>> Use device ID 41
>
> Thanks for submitting that. I should have been my duty, but I've been
> too busy w/ other things.
>
> You've probably already seen my spec in the Linux virtio-gpio patch
> queue. Feel free to texify it for submitting here. (*1)
>
> Also please remind me to update the device id (need to fix kernel as
> well as qemu side).
>
>
> --mtx
>
> *1) 
> https://github.com/metux/linux/commit/66c98eab3433a592b11d60d1a05c2609fee4811a
> https://github.com/metux/linux/tree/submit/virtio-gpio-2020-12-07-v3
>

Has anyone ever tried to use GPIO in the guest to generate waveform ?

When the frequency reaches a certain level, the waveform will become 
inaccurate
due to the delay and uncertainty of the communication time between 
virtio frontend
and backend. I'm not sure if any good solution for this case.

Regards,
Jie

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/


  parent reply	other threads:[~2021-06-04  2:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  6:42 [virtio-comment] [PATCH] Reserve device id for GPIO device Viresh Kumar
2021-06-02  6:44 ` [virtio-comment] " Viresh Kumar
2021-06-02 11:57 ` Enrico Weigelt, metux IT consult
2021-06-02 12:11   ` Viresh Kumar
2021-06-04  2:28   ` Jie Deng [this message]
2021-06-04  3:33     ` Viresh Kumar
2021-06-04 10:58     ` 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=e0bb902f-d009-8aa1-0c71-25989d3d1269@intel.com \
    --to=jie.deng@intel.com \
    --cc=alex.bennee@linaro.org \
    --cc=bill.mills@linaro.org \
    --cc=info@metux.net \
    --cc=lkml@metux.net \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@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.