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