Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp260707ybi; Wed, 29 May 2019 20:52:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqyat6X4Na0AECfru5a+sKdqZOYCXG/T7GLhDADfe1EWInjXuF9na0v6YdfYYeo/huUpReLy X-Received: by 2002:aa7:8b4d:: with SMTP id i13mr1599174pfd.233.1559188364294; Wed, 29 May 2019 20:52:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559188364; cv=none; d=google.com; s=arc-20160816; b=QHl3WVt+aUlPWdW6xlvlMFPP0q8SE2wtsSsc42B1fgeMUlBzsMXZ3c3S3mEA3VRviA a9b4Zlyb8DvUXTBTxCLmKeYXtrYFqu8aflfaC8Nwsk4yY57ZWVTDvXfmO5nIWyIkhLMY XwAjY0FXFqjMoT3UMDeQ1XGjK3ilwIZ2ek8yFuo/1tfnm92crGzvaqvC+KeUOaZ2MMem MfI5/OunZ254gdH65nuDlXh/2/UVm5ZJH3MJ0YuMzyJ7JW8uhg+hybgZd7xZyVdsR7j8 giM+MXvLGj+zQwoVulLUVuTYQZfivu6vdTqXO6FX94KAA9/7touL6/oMI2Iy9QgHw0C/ qLzQ== 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=HXtyP9J5S4cfhDeoEtNA2NuiotgpE1vfGp64wD3PK44=; b=ylQAV6KVdzYZiKNKE1V7Xc/rW40iuIoHRqZ4QmKtffGGwjyG7mhQ3BsUUgvG4voJ+Z PIKGkgtvug/e0hBnR2SDlQLpD7tflStmMFbXPkJElYRxHah2M9mfct4XkplLhWSAzSq6 PuqjJ9DgJNk2m37gUiSL8K1qAU9A8nOSz3exfkmnbG0JQ4i0fgtquem7VNFGUcfNcC2l sg9HXfLzZqkRhhVP5Fp5H/BUB3bbX7rWmFHnYI7nMIYhcJBObrfB96d7/uDFZgsKUjzY bz8ROVq40fUnFeTFnb2RVEoOGLgiMV4wIjC+DzDiQZhuXcufFs1qQSZmmFBU4ZdavFBY V3AQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=EUM0tvqR; 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 cd5si2461663plb.400.2019.05.29.20.52.29; Wed, 29 May 2019 20:52:44 -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=EUM0tvqR; 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 S2387400AbfE3Duq (ORCPT + 99 others); Wed, 29 May 2019 23:50:46 -0400 Received: from mail.kernel.org ([198.145.29.99]:57126 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732068AbfE3DTy (ORCPT ); Wed, 29 May 2019 23:19:54 -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 DE8BB248C9; Thu, 30 May 2019 03:19:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559186394; bh=7gEsUW+smFInOdwsEf1s8wZG5Cnp9Q1luH1uXAhA+10=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=EUM0tvqRdWeufPJRwTRbkYdpIMuKDi/BJ2kj6Bwcvqutk8J1I7L94mhkmlvwBru9g jUz8TziFasu9TbENFHcrq1ti8lLxZa2A6hIATGMN4i3SpKoy8aypGDWLCiqHhb0yUS /xNOznvirg+13dFTL4QizMKVwzlvzc7+Sec2VK50= 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.14 123/193] PM / core: Propagate dev->power.wakeup_path when no callbacks Date: Wed, 29 May 2019 20:06:17 -0700 Message-Id: <20190530030505.637068652@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190530030446.953835040@linuxfoundation.org> References: <20190530030446.953835040@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 d16b40cd26cc9..a30ff97632a54 100644 --- a/drivers/base/power/main.c +++ b/drivers/base/power/main.c @@ -1485,6 +1485,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