OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [virtio-comment] Re: [PATCH] Reserve device id for GPIO device

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


*1) https://github.com/metux/linux/commit/66c98eab3433a592b11d60d1a05c2609fee4811a

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.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]