< Home | Return to Ballot listing

Ballot Details    TC Member Ballot View
Resolve Issue #112: i2c: Allow buffer less transactions

Should the TC accept changes listed in the description to resolve issue 112, for inclusion in specification version(s) "virtio-v1.2-cs01", and future versions of the specification?

Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.

I move that:
The TC agrees to resolve the following specification issue:
Issue #112: i2c: Allow buffer less transactions
--------------------------------------
The I2C protocol allows zero-length requests with no data, like the
SMBus Quick command, where the command is inferred based on the
read/write flag itself.

In order to allow such a request, allocate another bit,
VIRTIO_I2C_FLAGS_M_RD(1), in the flags to pass the request type, as read
or write. This was earlier done using the read/write permission to the
buffer itself.

This still won't work well if multiple buffers are passed for the same
request, i.e. the write-read requests, as the VIRTIO_I2C_FLAGS_M_RD flag
can only be used with a single buffer.

Coming back to it, there is no need to send multiple buffers with a
single request. All we need, is a way to group several requests
together, which we can already do based on the
VIRTIO_I2C_FLAGS_FAIL_NEXT flag.

Remove support for multiple buffers within a single request.

Add a new feature flag for zero length requests and make it mandatory
for it to be implemented, so we don't need to drag the old
implementation around.

Here is the patch to update spec:
https://lists.oasis-open.org/archives/virtio-dev/202110/msg00109.html
--------------------------------------

The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-dev/202110/msg00109.html
--------------------------------------

The TC agrees to include the above change(s) in specification version(s) "virtio-v1.2-cs01", and future versions of the
specification.

--------------------------------------

Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.

--------------------------------------

 [ ]  Yes
 [ ]  No
 [ ]  Abstain
Opening:   Thursday, 21 October 2021 @ 06:45 am EDT
Closing:   Thursday, 28 October 2021 @ 06:45 am EDT
Group:   OASIS Virtual I/O Device (VIRTIO) TC
Ballot has closed.

Referenced Items
Name Type Date Action
Document
2021-10-28

Voting Details

Voting Summary

Options with highest number of votes are bold

Option # Votes % of Total
Yes 4 100%
No 0 0%
Abstain 4
Eligible members who have voted: 4 of 8 50%
Eligible members who have abstained: 4 of 8 50%
Eligible members who have not voted: 0 of 8 0%

Voting Details

Voter Company VoteReference Document and/or Comment
Enrico Granata
Google Inc.
Abstain
 
Halil Pasic
IBM
Abstain
 
Matti Moell
OpenSynergy GmbH
Abstain
 
Mihai Carabas
Oracle
Yes
 
Stefan Hajnoczi
Red Hat
Abstain
 
Michael S. Tsirkin
Red Hat
Yes
 
Cornelia Huck
Red Hat
Yes
 
Jan Kiszka
Siemens AG
Yes