From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from saturn.retrosnub.co.uk ([178.18.118.26]:41656 "EHLO saturn.retrosnub.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753150AbcHOPtx (ORCPT ); Mon, 15 Aug 2016 11:49:53 -0400 Subject: Re: [PATCH v4 5/7] iio: hid-sensors: use asynchronous resume To: Dmitry Torokhov References: <1470561939-14278-1-git-send-email-srinivas.pandruvada@linux.intel.com> <1470561939-14278-6-git-send-email-srinivas.pandruvada@linux.intel.com> <884e74df-569e-8218-fbda-f9c7ecfe1e5a@kernel.org> Cc: Jiri Kosina , Srinivas Pandruvada , "linux-input@vger.kernel.org" , linux-iio@vger.kernel.org From: Jonathan Cameron Message-ID: <6ee7950c-8602-a4a1-b87c-0e6a60752c50@kernel.org> Date: Mon, 15 Aug 2016 16:49:51 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org On 15/08/16 16:45, Dmitry Torokhov wrote: > On Mon, Aug 15, 2016 at 7:52 AM, Jonathan Cameron wrote: >> On 15/08/16 15:07, Jonathan Cameron wrote: >>> On 07/08/16 11:15, Jiri Kosina wrote: >>>> On Sun, 7 Aug 2016, Srinivas Pandruvada wrote: >>>> >>>>> Some platforms power off sensor hubs during S3 suspend, which will require >>>>> longer time to resume. This hurts system resume time, so resume >>>>> asynchronously. >>>>> >>>>> Signed-off-by: Srinivas Pandruvada >>>> >>>> Jonathan, are you going to cherry-pick this patch from the series? >>>> Alternatively, if you're okay with it, I can pull it in together with the >>>> whole set with your Acked-by or Reviewed-by. >>>> >>> I'll take it via IIO. Got a bit of catching up to do (been on holiday) >> Applied to the togreg branch of iio.git - initially pushed out as >> testing for the autobuilders to play with it. >> This one is not really connected to the others so makes sense to >> take it separately. >> >> I'm out of my depth on the rest of the patches in this series >> and don't have time to learn enough to follow them! Sorry I >> can't help on that front. > > About this patch: me sees a new work, me does not see new calls to > cancel_work_sync() or flush_work() anywhere, me gets worried. > > Thanks. Good point. Backed out for now... Jonathan >