All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jie Deng <jie.deng@intel.com>
Cc: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
	virtio-comment@lists.oasis-open.org,
	"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 09:03:44 +0530	[thread overview]
Message-ID: <20210604033344.c2tnt7upv7y3soaq@vireshk-i7> (raw)
In-Reply-To: <e0bb902f-d009-8aa1-0c71-25989d3d1269@intel.com>

On 04-06-21, 10:28, Jie Deng wrote:
> Has anyone ever tried to use GPIO in the guest to generate waveform ?

I haven't tried the code yet, I just started where Enrico left
earlier. Done with Id allocation and specs (yes reviews pending), will
be looking into kernel now.

> 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.

This is expected I would say. The interface is going to be slow and at
some frequency it will break the waveform.

-- 
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-04  3:33 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
2021-06-04  3:33     ` Viresh Kumar [this message]
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=20210604033344.c2tnt7upv7y3soaq@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=bill.mills@linaro.org \
    --cc=info@metux.net \
    --cc=jie.deng@intel.com \
    --cc=lkml@metux.net \
    --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.