[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c8bf7c3-1aa4-e5fb-74e4-7117d6d43444@linux.intel.com>
Date: Mon, 8 Jan 2018 16:33:07 +0200
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux PM <linux-pm@...r.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Kevin Hilman <khilman@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
linux-i2c <linux-i2c@...r.kernel.org>,
Linux PCI <linux-pci@...r.kernel.org>,
Lee Jones <lee.jones@...aro.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Wolfram Sang <wsa@...-dreams.de>
Subject: Re: [PATCH 0/7] PM / core: Direct handling of DPM_FLAG_SMART_SUSPEND
and DPM_FLAG_LEAVE_SUSPENDED
On 01/03/2018 02:29 AM, Rafael J. Wysocki wrote:
> Resending the original series (except for the first patch that has been
> applied already) along with some driver code changes based on them as
> requested by Ulf.
>
> The driver patches are an intel-lpss change (already reviewed), two
> modifications of i2c-designware-platdrv (posted previously but slightly
> changed since then) and a PCIe port driver change.
>
> At this point patches [1-3/7] are pretty much on the way in and the driver
> material depends on review comments (it is pointless to apply [4/7] without
> [5-6/7], so it depends on them in my view).
>
> I'm sending this from a system running with all of the series applied, although
> admittedly not using i2c-designware-platdrv. However, one of my test machines
> has this one and I haven't seen any adverse effects of these changes on it so
> far.
>
Both i2cdetect and hexdump from touchscreen and touchpad devices were
working fine. I used linux-next next-20180108 and patches 4-7/7.
Tested-by: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Powered by blists - more mailing lists