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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F183EC43219 for ; Tue, 5 Apr 2022 11:08:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241520AbiDELJ2 (ORCPT ); Tue, 5 Apr 2022 07:09:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59452 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1353169AbiDEKFt (ORCPT ); Tue, 5 Apr 2022 06:05:49 -0400 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 385E2BE9D3; Tue, 5 Apr 2022 02:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1649152465; x=1680688465; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=FvrfFAwIBkVcQbb44q338G+GvCQgvfd7wKltudNp7nY=; b=hhOW0vpitTEhCP8nc2qeltOhLzwnDzEgjFoVOlq6WKo/MkNN8vZcojXN FE0bDOvgd2gW7m+F88iRODUsH1GyVrmWrTr/Vs9J3VZetdLwXonY/p4u7 Ius0XkJI+OSRMCMjI1Coz4WWeUMI8A2idxgEwiA6CffOdh0TPbnIBHIum UqL+xCpg/ujcZlexuK7ZD6aiBQvni8oXv5yPIPT7P1JwLU+WagVQyvX2P wpDwVDc5XGE5EIjFUWywBeWIeqWtAuItnv4yNJb3+oG8/Utf2pUK52Mid j2XasMRuahzsz7JZAP1mQbcCKwT9NZjpfVSn+7nz6Hg/7vJZdxx78RXfc w==; X-IronPort-AV: E=McAfee;i="6200,9189,10307"; a="347150668" X-IronPort-AV: E=Sophos;i="5.90,236,1643702400"; d="scan'208";a="347150668" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Apr 2022 02:54:24 -0700 X-IronPort-AV: E=Sophos;i="5.90,236,1643702400"; d="scan'208";a="556460066" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.162]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Apr 2022 02:54:21 -0700 Received: by lahna (sSMTP sendmail emulation); Tue, 05 Apr 2022 12:54:19 +0300 Date: Tue, 5 Apr 2022 12:54:19 +0300 From: Mika Westerberg To: "Rafael J. Wysocki" Cc: Linux PCI , Linux PM , LKML , Bjorn Helgaas Subject: Re: [PATCH v1 2/2] PCI: PM: Resume bus after putting the bridge into D0 entirely Message-ID: References: <4198163.ejJDZkT8p0@kreacher> <1807986.atdPhlSkOF@kreacher> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1807986.atdPhlSkOF@kreacher> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Mon, Apr 04, 2022 at 05:42:27PM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > It is rather counter-intuitive to attempt to resume devices on a bus > segment before completing a transition of their parent bridge into > D0, so do that when the transition is complete. > > This matters especially when the transition in question is not > successful, in which case it doesn't make sense to even try to > resume the child devices at all. Good point. > Signed-off-by: Rafael J. Wysocki Reviewed-by: Mika Westerberg