From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jie Deng <jie.deng@intel.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, cohuck@redhat.com
Subject: Re: [virtio-comment] [PATCH v4] virtio-i2c: add the device specification
Date: Tue, 10 Nov 2020 05:33:21 -0500 [thread overview]
Message-ID: <20201110053225-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <83052aa7-8815-ce9d-3c9f-59d863107702@redhat.com>
On Tue, Nov 10, 2020 at 09:05:47AM +0100, Paolo Bonzini wrote:
> On 10/11/20 08:31, Jie Deng wrote:
> > virtio-i2c is a virtual I2C adapter device. It provides a way to flexibly
> > communicate with the I2C slave devices from the guest. This patch adds
> > the specification for this device.
>
> Sorry I didn't reply last week, but I really would prefer if virtio-i2c
> supported write-read transactions.
>
> Paolo
And I think an easier way is to allow multi-segment transactions
probably using the stop flag.
--
MST
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2020-11-10 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 7:31 [virtio-comment] [PATCH v4] virtio-i2c: add the device specification Jie Deng
2020-11-10 8:05 ` Paolo Bonzini
2020-11-10 10:33 ` Michael S. Tsirkin [this message]
2020-11-10 10:59 ` Paolo Bonzini
2020-11-12 1:51 ` Jie Deng
2020-11-12 8:54 ` Michael S. Tsirkin
2020-11-13 2:39 ` Jie Deng
2020-11-16 2:12 ` Jie Deng
2020-11-16 8:16 ` Paolo Bonzini
2020-11-17 6:55 ` Jie Deng
2020-11-17 8:23 ` Gerd Hoffmann
2020-11-17 15:59 ` Paolo Bonzini
2020-11-18 1:24 ` Jie Deng
2020-11-18 2:06 ` [virtio-comment] Re: [virtio-dev] " Jie Deng
2020-11-18 8:22 ` Paolo Bonzini
2020-11-19 1:41 ` Jie Deng
2020-11-19 15:55 ` Paolo Bonzini
2020-11-20 1:36 ` Jie Deng
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=20201110053225-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=jie.deng@intel.com \
--cc=pbonzini@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.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