[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8592a48d-0131-86bf-586a-d33e7989e523@intel.com>
Date: Mon, 1 Nov 2021 13:23:54 +0800
From: Jie Deng <jie.deng@...el.com>
To: Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc: Viresh Kumar <viresh.kumar@...aro.org>,
Greg KH <gregkh@...uxfoundation.org>,
Wolfram Sang <wsa@...nel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kernel <kernel@...s.com>, Conghui Chen <conghui.chen@...el.com>
Subject: Re: [PATCH 1/2] i2c: virtio: disable timeout handling
On 2021/10/29 20:24, Vincent Whitchurch wrote:
> On Thu, Oct 21, 2021 at 05:30:28AM +0200, Jie Deng wrote:
>> For this moment, we can solve the problem by using a hardcoded big
>> value or disabling the timeout.
> Is that an Acked-by on this patch which does the latter?
Yes, you can add my Acked-by. Let's see if other people still have
different opinions.
>
>> Over the long term, I think the backend should provide that timeout
>> value and guarantee that its processing time should not exceed that
>> value.
> If you mean that the spec should be changed to allow the virtio driver
> to be able to program a certain timeout for I2C transactions in the
> virtio device, yes, that does sound reasonable.
Due to changes in my work, I will pass my virtio-i2c maintenance to Conghui.
She may work on this in the future.
Powered by blists - more mailing lists