From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C34F2C04AB5 for ; Thu, 6 Jun 2019 14:36:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9E02120684 for ; Thu, 6 Jun 2019 14:36:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729080AbfFFOgO (ORCPT ); Thu, 6 Jun 2019 10:36:14 -0400 Received: from mga05.intel.com ([192.55.52.43]:8828 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728841AbfFFOgL (ORCPT ); Thu, 6 Jun 2019 10:36:11 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Jun 2019 07:36:10 -0700 X-ExtLoop1: 1 Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.157]) by fmsmga001.fm.intel.com with SMTP; 06 Jun 2019 07:36:07 -0700 Received: by lahna (sSMTP sendmail emulation); Thu, 06 Jun 2019 17:36:06 +0300 Date: Thu, 6 Jun 2019 17:36:06 +0300 From: Mika Westerberg To: "Rafael J. Wysocki" Cc: Bjorn Helgaas , "Rafael J. Wysocki" , Len Brown , Lukas Wunner , Keith Busch , Alex Williamson , Alexandru Gagniuc , ACPI Devel Maling List , Linux PCI Subject: Re: [PATCH 3/3] PCI / ACPI: Handle sibling devices sharing power resources Message-ID: <20190606143606.GN2781@lahna.fi.intel.com> References: <20190605145820.37169-1-mika.westerberg@linux.intel.com> <20190605145820.37169-4-mika.westerberg@linux.intel.com> <20190606112640.GA2781@lahna.fi.intel.com> <20190606134419.GL2781@lahna.fi.intel.com> <20190606141717.GM2781@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Thu, Jun 06, 2019 at 04:27:21PM +0200, Rafael J. Wysocki wrote: > On Thu, Jun 6, 2019 at 4:17 PM Mika Westerberg > wrote: > > > > On Thu, Jun 06, 2019 at 04:08:11PM +0200, Rafael J. Wysocki wrote: > > > That isn't necessary IMO as long as the device are not accessed. If > > > the kernel thinks that a given device is in D3cold and doesn't access > > > it, then it really doesn't matter too much what state the device is in > > > physically. On the first access the device should be reinitialized > > > anyway. > > > > But if the device is configured to wake. For example when it detects a > > hotplug that state is gone when it goes to D0unitialized. > > For this we'll need a pm_runtime_resume() of the dependent device on > the resource going "on". > > That means we need a list of devices to resume when the resource goes > "on" after being taken "off". OK, thanks.