[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YEGBeWHRfL4gN9pX@google.com>
Date: Thu, 4 Mar 2021 16:55:21 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: "jingle.wu" <jingle.wu@....com.tw>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
linux-input <linux-input@...r.kernel.org>,
phoenix <phoenix@....com.tw>, "dave.wang" <dave.wang@....com.tw>,
"josh.chen" <josh.chen@....com.tw>
Subject: Re: [PATCH] Input: elan_i2c - Reduce the resume time for new dev ices
Hi Jingle,
On Tue, Mar 02, 2021 at 09:04:57AM +0800, jingle.wu wrote:
> HI Dmitry:
>
> So data->ops->initialize(client) essentially performs reset of the
> controller (we may want to rename it even) and as far as I understand
> you would want to avoid resetting the controller on newer devices,
> right?
>
> -> YES
>
> My question is how behavior of older devices differ from the new ones
> (are they stay in "undefined" state at power up) and whether it is
> possible to determine if controller is in operating mode. For example,
> what would happen on older devices if we call elan_query_product() below
> without resetting the controller?
>
> -> But there may be other problems, because ELAN can't test all the older devices ,
> -> so use quirk to divide this part.
OK, but could you please tell me what exactly was changed in the newer
parts behavior regarding need to reset after powering them on?
Thanks.
--
Dmitry
Powered by blists - more mailing lists