* [virtio-comment] [PATCH] Reserve device id for GPIO device
@ 2021-06-02 6:42 Viresh Kumar
2021-06-02 6:44 ` [virtio-comment] " Viresh Kumar
2021-06-02 11:57 ` Enrico Weigelt, metux IT consult
0 siblings, 2 replies; 7+ messages in thread
From: Viresh Kumar @ 2021-06-02 6:42 UTC (permalink / raw)
To: virtio-comment
Cc: Viresh Kumar, Vincent Guittot, Bill Mills, Alex Bennée,
Enrico Weigelt, metux IT consult
Use device ID 41
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
content.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/content.tex b/content.tex
index b9934b4fa05c..d9913d056317 100644
--- a/content.tex
+++ b/content.tex
@@ -2876,6 +2876,8 @@ \chapter{Device Types}\label{sec:Device Types}
\hline
40 & Bluetooth device \\
\hline
+41 & GPIO device \\
+\hline
\end{tabular}
Some of the devices above are unspecified by this document,
--
2.25.1
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/
^ permalink raw reply related [flat|nested] 7+ messages in thread
* [virtio-comment] Re: [PATCH] Reserve device id for GPIO device
2021-06-02 6:42 [virtio-comment] [PATCH] Reserve device id for GPIO device Viresh Kumar
@ 2021-06-02 6:44 ` Viresh Kumar
2021-06-02 11:57 ` Enrico Weigelt, metux IT consult
1 sibling, 0 replies; 7+ messages in thread
From: Viresh Kumar @ 2021-06-02 6:44 UTC (permalink / raw)
To: virtio-comment
Cc: Vincent Guittot, Bill Mills, Alex Bennée, Enrico Weigelt,
metux IT consult
On 02-06-21, 12:12, Viresh Kumar wrote:
> Use device ID 41
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> content.tex | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index b9934b4fa05c..d9913d056317 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -2876,6 +2876,8 @@ \chapter{Device Types}\label{sec:Device Types}
> \hline
> 40 & Bluetooth device \\
> \hline
> +41 & GPIO device \\
> +\hline
> \end{tabular}
>
> Some of the devices above are unspecified by this document,
Opened issue for the same here:
https://github.com/oasis-tcs/virtio-spec/issues/109
--
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/
^ permalink raw reply [flat|nested] 7+ messages in thread
* [virtio-comment] Re: [PATCH] Reserve device id for GPIO device
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
1 sibling, 2 replies; 7+ messages in thread
From: Enrico Weigelt, metux IT consult @ 2021-06-02 11:57 UTC (permalink / raw)
To: Viresh Kumar, virtio-comment
Cc: Vincent Guittot, Bill Mills, Alex Bennée, Enrico Weigelt,
metux IT consult
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
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
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/
^ permalink raw reply [flat|nested] 7+ messages in thread
* [virtio-comment] Re: [PATCH] Reserve device id for GPIO device
2021-06-02 11:57 ` Enrico Weigelt, metux IT consult
@ 2021-06-02 12:11 ` Viresh Kumar
2021-06-04 2:28 ` Jie Deng
1 sibling, 0 replies; 7+ messages in thread
From: Viresh Kumar @ 2021-06-02 12:11 UTC (permalink / raw)
To: Enrico Weigelt, metux IT consult
Cc: virtio-comment, Vincent Guittot, Bill Mills, Alex Bennée,
Enrico Weigelt, metux IT consult
On 02-06-21, 13: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)
I am halfway through :)
> Also please remind me to update the device id (need to fix kernel as
> well as qemu side).
Sure, I would be fine to re-spin the kernel driver as well (we need to
really finish this stuff sooner) :)
--
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/
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [virtio-comment] Re: [PATCH] Reserve device id for GPIO device
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
2021-06-04 10:58 ` Enrico Weigelt, metux IT consult
1 sibling, 2 replies; 7+ messages in thread
From: Jie Deng @ 2021-06-04 2:28 UTC (permalink / raw)
To: Enrico Weigelt, metux IT consult, Viresh Kumar, virtio-comment
Cc: Vincent Guittot, Bill Mills, Alex Bennée, Enrico Weigelt,
metux IT consult
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/
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [virtio-comment] Re: [PATCH] Reserve device id for GPIO device
2021-06-04 2:28 ` Jie Deng
@ 2021-06-04 3:33 ` Viresh Kumar
2021-06-04 10:58 ` Enrico Weigelt, metux IT consult
1 sibling, 0 replies; 7+ messages in thread
From: Viresh Kumar @ 2021-06-04 3:33 UTC (permalink / raw)
To: Jie Deng
Cc: Enrico Weigelt, metux IT consult, virtio-comment,
Vincent Guittot, Bill Mills, Alex Bennée, Enrico Weigelt,
metux IT consult
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/
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [virtio-comment] Re: [PATCH] Reserve device id for GPIO device
2021-06-04 2:28 ` Jie Deng
2021-06-04 3:33 ` Viresh Kumar
@ 2021-06-04 10:58 ` Enrico Weigelt, metux IT consult
1 sibling, 0 replies; 7+ messages in thread
From: Enrico Weigelt, metux IT consult @ 2021-06-04 10:58 UTC (permalink / raw)
To: virtio-comment
On 04.06.21 04:28, Jie Deng wrote:
> 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.
Wooow, that's something I didn't ever dared considering. How well that
works heavily depends on actual hardware (even on bare metal) and lots
of other factors.
Even on a bare metal Linux system, I wouldn't want userland do such
things via raw gpio devices - instead have specific (RT capable) kernel
drivers that expose themselves via some fitting hilevel subsys (eg. iio
or pwm). For those use cases, we should have specific protocols.
If it helps, we can add certain metadata, eg. timing constraints to the
line descriptions.
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
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/
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2021-06-04 10:58 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2021-06-04 10:58 ` Enrico Weigelt, metux IT consult
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.