[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGAzgso2Lf6Yw+5xGLkaTdJ7TAZ8_43qEpOya+zUjWqy4ET7RQ@mail.gmail.com>
Date: Fri, 27 Jul 2018 09:17:12 -0700
From: "dbasehore ." <dbasehore@...omium.org>
To: hdegoede@...hat.com
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>, wsa@...-dreams.de,
linux-i2c@...r.kernel.org, Doug Anderson <dianders@...omium.org>,
dtor@...omium.org,
venkateswarlu.v.vinjamuri@...el.corp-partner.google.com
Subject: Re: [PATCH] i2c: enable async suspend/resume on i2c devices
On Fri, Jul 27, 2018 at 5:07 AM Hans de Goede <hdegoede@...hat.com> wrote:
> Hi,
>
> On 07/27/2018 12:44 PM, Andy Shevchenko wrote:
> > On Fri, Jul 27, 2018 at 1:55 AM, Derek Basehore <dbasehore@...omium.org>
> wrote:
> >> This enables the async suspend property for i2c devices. This reduces
> >> the suspend/resume time considerably on platforms with multiple i2c
> >> devices (such as a trackpad or touchscreen).
> >
> > How did you test this?
>
It was tested on Apollolake Chromebook devices.
> >
> > Especially on Chromebooks based on Intel Cherrytrail / Braswell
> > platforms, they have a painful PMIC vs. OS design solution.
> >
> > +Cc: Hans, who did a lot in this area.
>
> We disable suspend of the i2c controller for the i2c-bus
> to which the PMIc is connected on these platforms, so I do not
> expect this to cause any new issues.
>
> But this is something to keep an eye on,
>
> Regards,
>
> Hans
>
>
Content of type "text/html" skipped
Powered by blists - more mailing lists