[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 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 frontendand 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 firstname.lastname@example.org -- +49-151-27565287