On 2020/11/19 23:55, Paolo Bonzini wrote:
On 19/11/20 02:41, Jie Deng wrote:
No, the kick is only an advice. The device is allowed to poll on
the ring and ignore kicks completely, for example.
Paolo
Understood. But I saw your proposal can only group two segments
"write-read".
What if we
On 19/11/20 02:41, Jie Deng wrote:
No, the kick is only an advice. The device is allowed to poll on the
ring and ignore kicks completely, for example.
Paolo
Understood. But I saw your proposal can only group two segments
"write-read".
What if we have segments more than two ? for example,
On 2020/11/18 16:22, Paolo Bonzini wrote:
On 18/11/20 03:06, Jie Deng wrote:
Can the "kick" be used for grouping ? I mean when a write and a read
are sent by one kick at a time, they will be treated as one
transaction by default if the host has such a feature bit.
No, the kick is only an ad
On 18/11/20 03:06, Jie Deng wrote:
Can the "kick" be used for grouping ? I mean when a write and a read
are sent by one kick at a time, they will be treated as one
transaction by default if the host has such a feature bit.
No, the kick is only an advice. The device is allowed to poll on the
On 2020/11/17 16:23, Gerd Hoffmann wrote:
On Tue, Nov 17, 2020 at 02:55:14PM +0800, Jie Deng wrote:
On 2020/11/16 16:16, Paolo Bonzini wrote:
On 16/11/20 03:12, Jie Deng wrote:
Fore example, the frontend may kick the sequence "write read read
..." to the backend at a time.
The segments can
On 2020/11/17 23:59, Paolo Bonzini wrote:
On 17/11/20 09:23, Gerd Hoffmann wrote:
That is not enough. You also need that for the transactions. If the
driver sends a write and a read message the device needs to know
whenever that is one or two transactions. So if you want continue
with the i
On 17/11/20 09:23, Gerd Hoffmann wrote:
That is not enough. You also need that for the transactions. If the
driver sends a write and a read message the device needs to know
whenever that is one or two transactions. So if you want continue
with the i2c_msg list idea you need some way to group y
On Tue, Nov 17, 2020 at 02:55:14PM +0800, Jie Deng wrote:
>
> On 2020/11/16 16:16, Paolo Bonzini wrote:
> > On 16/11/20 03:12, Jie Deng wrote:
> > > Fore example, the frontend may kick the sequence "write read read
> > > ..." to the backend at a time.
> > >
> > > The segments can be aggregated in
On 2020/11/16 16:16, Paolo Bonzini wrote:
On 16/11/20 03:12, Jie Deng wrote:
Fore example, the frontend may kick the sequence "write read read
..." to the backend at a time.
The segments can be aggregated into "i2c_msg list" and sent to the
hardware at a time by the backend.
The host nati
On 16/11/20 03:12, Jie Deng wrote:
Fore example, the frontend may kick the sequence "write read read ..."
to the backend at a time.
The segments can be aggregated into "i2c_msg list" and sent to the
hardware at a time by the backend.
The host native drivers will finally send these segments u
Hi Michael and Paolo,
Have you reached an agreement on the design of "virtio_i2c_req" ?
Personally, I think the design in v4 can already handle the
multi-segment transactions between frontend and backend.
Fore example, the frontend may kick the sequence "write read read ..."
to the backend a
On 2020/11/12 16:54, Michael S. Tsirkin wrote:
On Thu, Nov 12, 2020 at 09:51:17AM +0800, Jie Deng wrote:
On 2020/11/10 18:59, Paolo Bonzini wrote:
On 10/11/20 11:33, Michael S. Tsirkin wrote:
Sorry I didn't reply last week, but I really would prefer if virtio-i2c
supported write-read transac
On Thu, Nov 12, 2020 at 09:51:17AM +0800, Jie Deng wrote:
>
> On 2020/11/10 18:59, Paolo Bonzini wrote:
> > On 10/11/20 11:33, Michael S. Tsirkin wrote:
> > > > Sorry I didn't reply last week, but I really would prefer if virtio-i2c
> > > > supported write-read transactions.
> > >
> > > And I thi
On 2020/11/10 18:59, Paolo Bonzini wrote:
On 10/11/20 11:33, Michael S. Tsirkin wrote:
Sorry I didn't reply last week, but I really would prefer if virtio-i2c
supported write-read transactions.
And I think an easier way is to allow multi-segment transactions
probably using the stop flag.
Y
On 10/11/20 11:33, Michael S. Tsirkin wrote:
Sorry I didn't reply last week, but I really would prefer if virtio-i2c
supported write-read transactions.
And I think an easier way is to allow multi-segment transactions
probably using the stop flag.
You cannot always be sure that the host would
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.
>
> Sor
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
support
17 matches
Mail list logo
