From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752112AbeADJZP (ORCPT + 1 other); Thu, 4 Jan 2018 04:25:15 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:46958 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752099AbeADJZM (ORCPT ); Thu, 4 Jan 2018 04:25:12 -0500 Date: Thu, 4 Jan 2018 10:25:15 +0100 From: "gregkh@linuxfoundation.org" To: Vikas Bansal Cc: "Rafael J. Wysocki" , "Rafael J. Wysocki" , "len.brown@intel.com" , "pavel@ucw.cz" , "linux-pm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Anuj Gupta Subject: Re: [PATCH V3] PM: In kernel power management domain_pm created for async schedules Message-ID: <20180104092515.GB26245@kroah.com> References: <20171206120714epcms5p70081d5bc518c3bb5f9cca4f56b203abf@epcms5p7> <20171206141238.GB11339@kroah.com> <3785462.Nrr6Y8ermz@aspire.rjw.lan> <20171213084612epcms5p7755822fff34c87907de2236923e82305@epcms5p7> <20180104085900epcms5p6e6c7f3e8c0262e110dcd2fd3498fcd61@epcms5p6> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180104085900epcms5p6e6c7f3e8c0262e110dcd2fd3498fcd61@epcms5p6> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Thu, Jan 04, 2018 at 08:59:00AM +0000, Vikas Bansal wrote: > Sender : Rafael J. Wysocki > > Date : 2017-12-14 03:56 (GMT+5:30) > > > > > > On Wed, Dec 13, 2017 at 9:46 AM, Vikas Bansal > wrote: > >> > >> Sender : Rafael J. Wysocki > >> Date : 2017-12-06 19:48 (GMT+5:30) > >> > >>> > >>> Also it is not clear to me if this fixes a mainline kernel issue, > >>> because the changelog mentions a driver doing something odd, but it > >>> doesn't say which one it is and whether or not it is in the tree. > >> > >> No, this driver is not part of mainline yet. > > > > So please submit it along with the driver that needs it, whenever that > > one is ready. > > > > Thanks, > > Rafael > > I am not sure when that driver will be submitted to open source and I even > don't know whether final implementation of driver will have async_schedules or > not. I just found one optimization in PM core because of that driver. If there > is any issue with patch, please let me know. I will correct. We can't take the patch without the driver at the same time, sorry. greg k-h