Displaying 4 results from an estimated 4 matches for "ic2_hdr".
Did you mean:
ecp_hdr
2020 Sep 08
1
[PATCH] i2c: virtio: add a virtio i2c frontend driver
...i2c_msg {
>>>> +??? struct virtio_i2c_hdr hdr;
>>>> +??? char *buf;
>>>> +??? u8 status;
>>>
>>>
>>> Any reason for separating status out of virtio_i2c_hdr?
>>>
>> The status is not from i2c_msg.
>
>
> You meant ic2_hdr? You embed status in virtio_i2c_msg anyway.
>
>
The "i2c_msg" structure defined in i2c.h.
>> So I put it out of virtio_i2c_hdr.
>
>
> Something like status or response is pretty common in virtio request
> (e.g net or scsi), if no special reason, it's better t...
2020 Sep 04
2
[PATCH] i2c: virtio: add a virtio i2c frontend driver
On 2020/9/4 12:06, Jason Wang wrote:
>
>> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
>> index 293e7a0..70c8e30 100644
>> --- a/drivers/i2c/busses/Kconfig
>> +++ b/drivers/i2c/busses/Kconfig
>> @@ -21,6 +21,17 @@ config I2C_ALI1535
>> ??????? This driver can also be built as a module.? If so, the module
>> ??????? will be called
2020 Sep 04
2
[PATCH] i2c: virtio: add a virtio i2c frontend driver
On 2020/9/4 12:06, Jason Wang wrote:
>
>> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
>> index 293e7a0..70c8e30 100644
>> --- a/drivers/i2c/busses/Kconfig
>> +++ b/drivers/i2c/busses/Kconfig
>> @@ -21,6 +21,17 @@ config I2C_ALI1535
>> ??????? This driver can also be built as a module.? If so, the module
>> ??????? will be called
2020 Sep 07
0
[PATCH] i2c: virtio: add a virtio i2c frontend driver
...gt;
>>>
>>> +struct virtio_i2c_msg {
>>> +??? struct virtio_i2c_hdr hdr;
>>> +??? char *buf;
>>> +??? u8 status;
>>
>>
>> Any reason for separating status out of virtio_i2c_hdr?
>>
> The status is not from i2c_msg.
You meant ic2_hdr? You embed status in virtio_i2c_msg anyway.
> So I put it out of virtio_i2c_hdr.
Something like status or response is pretty common in virtio request
(e.g net or scsi), if no special reason, it's better to keep it in the hdr.
>
>>
>>> +};
>>> +
>>>...