Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jie Deng <jie.deng@intel.com>, Wolfram Sang <wsa@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: "Vincent Guittot" <vincent.guittot@linaro.org>,
	"Jason Wang" <jasowang@redhat.com>,
	"Bill Mills" <bill.mills@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	virtio-dev@lists.oasis-open.org,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [virtio-dev] Re: [PATCH] virtio: i2c: Allow buffer less transactions
Date: Mon, 16 Aug 2021 11:33:22 +0200	[thread overview]
Message-ID: <871r6tvin1.fsf@redhat.com> (raw)
In-Reply-To: <20210806042116.ji6n4j4vswvotnjh@vireshk-i7>

On Fri, Aug 06 2021, Viresh Kumar <viresh.kumar@linaro.org> wrote:

> On 23-07-21, 10:56, Viresh Kumar wrote:
>> The I2C protocol allows 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.
>> 
>> Since we are at very early stage of development currently, we can do
>> these modifications without addition of new features or versioning of
>> the protocol.
>> 
>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>> ---
>
> Gentle reminder!

Hm, I thought there had been some feedback already? I've been waiting
for a respin.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2021-08-16  9:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23  5:26 [PATCH] virtio: i2c: Allow buffer less transactions Viresh Kumar
2021-07-27  5:37 ` Viresh Kumar
2021-07-29  5:39 ` [virtio-dev] " Jie Deng
2021-07-29  5:47   ` Viresh Kumar
2021-07-29  6:18     ` [virtio-dev] " Jie Deng
2021-07-29  6:28       ` Viresh Kumar
2021-07-29  6:36         ` Jie Deng
2021-08-06  4:21 ` Viresh Kumar
2021-08-16  9:33   ` Cornelia Huck [this message]
2021-08-16  9:48     ` Viresh Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871r6tvin1.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bill.mills@linaro.org \
    --cc=jasowang@redhat.com \
    --cc=jie.deng@intel.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wsa@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox