From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: ACPI device using sub-resource of PCI device Date: Tue, 16 Aug 2016 15:20:18 +0300 Message-ID: <20160816122018.GK1751@lahna.fi.intel.com> References: <3103060.86QBTjSLk3@vostro.rjw.lan> <3861743.KWBechkp08@vostro.rjw.lan> <20160816091502.GB1751@lahna.fi.intel.com> <1471346604.4887.120.camel@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from mga14.intel.com ([192.55.52.115]:14767 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750803AbcHPMUW (ORCPT ); Tue, 16 Aug 2016 08:20:22 -0400 Content-Disposition: inline In-Reply-To: <1471346604.4887.120.camel@linux.intel.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Andy Shevchenko Cc: Aaron Durbin , "Rafael J. Wysocki" , Bjorn Helgaas , "Rafael J. Wysocki" , ACPI Devel Maling List , Linux PCI On Tue, Aug 16, 2016 at 02:23:24PM +0300, Andy Shevchenko wrote: > On Tue, 2016-08-16 at 12:15 +0300, Mika Westerberg wrote: > > On Fri, Aug 12, 2016 at 11:45:30AM -0500, Aaron Durbin wrote: > > > > > > Was anyone able to take a look into a solution for the current > > > problem?  Again, please feel free to ask if anyone would like help > > > testing potential solutions. > > > > Below is one proposal for fixing the issue. It is just a prototype and > > I'm not sure if it takes everything needed into account. Would you be > > able to try it out and let us know if it works for you? > > Just style comments below. Thanks for the comments. As Rafael already mentioned, this is just a prototype. We don't even know yet if it fixes the issue. If it turns out to be working and we decide to go with this approach, I will clean up the code accordingly and submit it as a proper patch.