Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp245708ybi; Wed, 29 May 2019 20:33:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqzqo6TrQngQMPLnSFZPmHWIYv6o81plcrIvpzLpTiudab6GeZ+29ppFqT6FBByRKDLL9p+z X-Received: by 2002:a17:90a:30a1:: with SMTP id h30mr1464001pjb.14.1559187200929; Wed, 29 May 2019 20:33:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559187200; cv=none; d=google.com; s=arc-20160816; b=h5y+WJPIpy+VvnxztwhecAabH1iYiakLvGhNbzkvNQY5SaD5lgn1sSDBTY+7vdB6yW KupuRQQSyVT6+tXph+VLpwkArLYUSoykhXZNYDIRUIuEvqIsyNghefLVvKQYvTeabdoT LmBKD4ixzLDTGDXTUkN6JMz4KwlCuMf/3HcHEm1gdLAqZW9huH8wko4KGrIhDmZIMPtX TBdLWD162mN563IDR69YGrJdpW33t5zQBxTz8tenuKadWocK7kvjVEdRqdaEzwPMJB+D 1X/KZ3o2lfHpSv0LVNZNUC006HMWyxPdmuj+nD7DJIKi8Y9FDN4CFAik5HcxhIkJg8lH UOLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=1ZzagFEJfczNlneo+Wlhg4YYnKn6qdkaAUv36bsBg6I=; b=PG6MwKCFFxV4VM79i1aYNUgxi9NayVonrdPU3vc0/A8Wtb3sToYi7a+XNqD6b0fOVX yWXULtvvojk0Y4+RMI9OsIAwFiyrjDyPSYJzjO3PNt1ghccv0no2DtlTXojiV5lezsey +O1M8+lyzczosYPz3CmCybQsPhCuj7+sIYjbVWLnMTTihAvQO2BemdZjqGYOdUUaEXMp ph6SS6USCMWCpzUdeQGZyPX2Ot8Y8rIB6y6kQ9l5vI/X5pxKRqGbZ/GhYMaO9clyodk2 aIqKw8VT8tELKsnSe6ncGQqBp+PHJvYpfIC/xwmHRsuGLkwVewXnZpn8IuLy4ckPGjlI +SbA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MTSX9EUt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y4si2377394pfq.10.2019.05.29.20.33.04; Wed, 29 May 2019 20:33:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MTSX9EUt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388595AbfE3Da3 (ORCPT + 99 others); Wed, 29 May 2019 23:30:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:35036 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731537AbfE3DV3 (ORCPT ); Wed, 29 May 2019 23:21:29 -0400 Received: from localhost (ip67-88-213-2.z213-88-67.customer.algx.net [67.88.213.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 44ECA249E6; Thu, 30 May 2019 03:21:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559186489; bh=lIVMaLhmshgVfq45JXAYLYb6R1A9DPD6T82LQI64QZ4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=MTSX9EUtZaDc+ng3q0HmnB+Of7OqC3B216P2Nm46uuDKHfVj8tN3j8VK7Cb14ymLv d6gGnHcdKHx7s4IqD81KWPYeWBv98/IR9RgMrOy5zzCiaIUYJ9M9om7K0kbCt6UPuA kVQkCJ1B/w7+AjumqtotUrg/1QXXdrIWVRZ3eu4Y= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Loic Pallardy , Ulf Hansson , "Rafael J. Wysocki" , Sasha Levin Subject: [PATCH 4.9 082/128] PM / core: Propagate dev->power.wakeup_path when no callbacks Date: Wed, 29 May 2019 20:06:54 -0700 Message-Id: <20190530030449.649947405@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190530030432.977908967@linuxfoundation.org> References: <20190530030432.977908967@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ Upstream commit dc351d4c5f4fe4d0f274d6d660227be0c3a03317 ] The dev->power.direct_complete flag may become set in device_prepare() in case the device don't have any PM callbacks (dev->power.no_pm_callbacks is set). This leads to a broken behaviour, when there is child having wakeup enabled and relies on its parent to be used in the wakeup path. More precisely, when the direct complete path becomes selected for the child in __device_suspend(), the propagation of the dev->power.wakeup_path becomes skipped as well. Let's address this problem, by checking if the device is a part the wakeup path or has wakeup enabled, then prevent the direct complete path from being used. Reported-by: Loic Pallardy Signed-off-by: Ulf Hansson [ rjw: Comment cleanup ] Signed-off-by: Rafael J. Wysocki Signed-off-by: Sasha Levin --- drivers/base/power/main.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c index 98517216879d5..a2714890fe431 100644 --- a/drivers/base/power/main.c +++ b/drivers/base/power/main.c @@ -1383,6 +1383,10 @@ static int __device_suspend(struct device *dev, pm_message_t state, bool async) if (dev->power.syscore) goto Complete; + /* Avoid direct_complete to let wakeup_path propagate. */ + if (device_may_wakeup(dev) || dev->power.wakeup_path) + dev->power.direct_complete = false; + if (dev->power.direct_complete) { if (pm_runtime_status_suspended(dev)) { pm_runtime_disable(dev); -- 2.20.1