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] [PATCH V2] virtio-gpio: add the device specification


On 07.06.21 07:42, Viresh Kumar wrote:

I guess in this case, it might be just a feature like VIRTIO_GPIO_F_BULK?

Oh yes, it makes sense. So we don't really need a _version_ here, but
can just keep on adding more and more features.

If newly added features are orthogonal, that would do the job.

I'm not familiar with GPIO, but a question is, consider we have virtqueue,
so actually bulking is already supported?

Virtqueue is there yes, but we don't have operations here yet (in this
version of the spec) which support setting 10 GPIO pins in output mode
with a single request from driver to device.

I think Enrico was looking to have a way to add provision for such
operations later on if required.

Yes. Newer versions of the protocol could add more operations like
setting a bunch of gpios at once (only some HW really supports that, so
we yet have to sort out whether that should be blindly emulation by host
or refused - depending on how well this fits in to timing requirements).
Other new things could be configuring pullup/down (which has some
overlap with pinmux - some hw does it in the gpio controller, some by
separate pinmux), debounce filters, level thresholds, etc, etc ...

For now we're doing just the very basics - switch on/off, perhaps get an
irq if input changes. The more complex, not so common stuff is left for
future revisions. And to do that, we need to tell the driver what is
supported by the device.

If there's a more granular way instead of just a version number, am
very fine with that. (A little example would be very appreciated).

OTOH, I don't think that an practically not used version field does
hurt so bad.


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


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