Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp482092ybl; Wed, 4 Dec 2019 06:05:53 -0800 (PST) X-Google-Smtp-Source: APXvYqwmkRQweEX/OIWtarITqJNFFzHwEqCnPjiIrquyoJVJaG5GzTVUhRtdWxwBx3COWOr+Y+o2 X-Received: by 2002:a9d:4d01:: with SMTP id n1mr2362046otf.245.1575468353153; Wed, 04 Dec 2019 06:05:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575468353; cv=none; d=google.com; s=arc-20160816; b=XOoSW0HjnXY165F3e4GJqlTLwegKCRDBBv+SELhl51YBLzF+/jUJwyA9zyazdufL7x zLQgLEIJdEllyzh4qxCmbwO/HcDuYsdfd+3MhmJ/Cie5G/qpKTcGoO+Yx1iUjhnMGQRx hyB/NwBKVTkISm12sbum4pqSCP5GW9y8NStBY+hFDF9Ru8VlLdZO44Kmkf5u9a0URlek j4/aHdDK6d46FLCCQc9xmcCsHjkAkqtwGozL7y6F+4OMzoGJ+63guA4T7KalCW/3Gjgz LGrkIvX3e6+F9XlAcuhMKx/M5Gol7A8UHWVB2mgbLiZap3cHbOa97IcffXr7yLyOrch0 F1uA== 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 :references:in-reply-to:date:cc:to:from:subject:message-id; bh=t84SZIjXbYRp6DkFIZ1tT4SCphKEFEMPN6ipk1ZltfQ=; b=Bv+F8Vx6mvn8ZVAmaR7jHvs/DF37eG3saMNYN8cKlEhxjX9a61FP1ZNtlUb+XcBYeg gwHRW45St5XYezdZiPy/KQ/ExW3gwvfbjP+KvfiOl1J+MSnNSKAJVcyuH0AVajs6jycS 62mKcoGl4/3pNm+2kjcMXN5TjUkZMK5mYtFSLMpVTu9fNfovZ1S/IUSLamAVK9M6x00i O8BBUFbIpJ4+HiFckIkc3zIGD140OZPUEcugAG1/uU3DxmqmNe1HJTwJbTRpjjf6dBPH vFVA/+OoPb6b+iCOGOB5lc90g+qixhfUJYCQ88zGWpHQt2uuDhpvFt6CKSkoAMNJuwcm oOJQ== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d3si3057010oti.56.2019.12.04.06.05.27; Wed, 04 Dec 2019 06:05:53 -0800 (PST) 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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727965AbfLDOEZ (ORCPT + 99 others); Wed, 4 Dec 2019 09:04:25 -0500 Received: from mga05.intel.com ([192.55.52.43]:26902 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727828AbfLDOEZ (ORCPT ); Wed, 4 Dec 2019 09:04:25 -0500 X-Amp-Result: SKIPPED(no attachment in message) 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; 04 Dec 2019 06:04:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,277,1571727600"; d="scan'208";a="218933982" Received: from yuanwan1-mobl.ccr.corp.intel.com ([10.249.174.225]) by fmsmga001.fm.intel.com with ESMTP; 04 Dec 2019 06:04:22 -0800 Message-ID: <2991d01601fdbcf25d745a387eda74926f1192b2.camel@intel.com> Subject: Re: [PATCH] ACPI: PM: Avoid attaching ACPI PM domain to certain devices From: Zhang Rui To: "Rafael J. Wysocki" , Linux ACPI Cc: LKML , Linux PM , "Brandt, Todd E" Date: Wed, 04 Dec 2019 22:04:23 +0800 In-Reply-To: <1773028.iBGNyVBcMc@kreacher> References: <1773028.iBGNyVBcMc@kreacher> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2019-12-04 at 02:54 +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Certain ACPI-enumerated devices represented as platform devices in > Linux, like fans, require special low-level power management handling > implemented by their drivers that is not in agreement with the ACPI > PM domain behavior. That leads to problems with managing ACPI fans > during system-wide suspend and resume. > > For this reason, make acpi_dev_pm_attach() skip the affected devices > by adding a list of device IDs to avoid to it and putting the IDs of > the affected devices into that list. > > Fixes: e5cc8ef31267 (ACPI / PM: Provide ACPI PM callback routines for > subsystems) > Reported-by: Zhang Rui > Cc: 3.10+ # 3.10+ > Signed-off-by: Rafael J. Wysocki > --- > > Rui, > > Please test this on the machine(s) affected by the fan suspend/resume > issues. Sure, Todd and I will re-run stress test with this patch applied when 5.5-rc1 released. thanks, rui > > I don't really see any cleaner way to address this problem, because > the > ACPI PM domain should not be used with the devices in question even > if > the driver that binds to them is not loaded. > > Cheers, > Rafael > > --- > drivers/acpi/device_pm.c | 12 +++++++++++- > 1 file changed, 11 insertions(+), 1 deletion(-) > > Index: linux-pm/drivers/acpi/device_pm.c > =================================================================== > --- linux-pm.orig/drivers/acpi/device_pm.c > +++ linux-pm/drivers/acpi/device_pm.c > @@ -1314,9 +1314,19 @@ static void acpi_dev_pm_detach(struct de > */ > int acpi_dev_pm_attach(struct device *dev, bool power_on) > { > + /* > + * Skip devices whose ACPI companions match the device IDs > below, > + * because they require special power management handling > incompatible > + * with the generic ACPI PM domain. > + */ > + static const struct acpi_device_id special_pm_ids[] = { > + {"PNP0C0B", }, /* Generic ACPI fan */ > + {"INT3404", }, /* Fan */ > + {} > + }; > struct acpi_device *adev = ACPI_COMPANION(dev); > > - if (!adev) > + if (!adev || !acpi_match_device_ids(adev, special_pm_ids)) > return 0; > > /* > > >