public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Manyi Li <limanyi@uniontech.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Sasha Levin <sashal@kernel.org>,
	rafael@kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH AUTOSEL 4.14 08/12] ACPI: PM: save NVS memory for Lenovo G40-45
Date: Sun,  7 Aug 2022 21:39:38 -0400	[thread overview]
Message-ID: <20220808013943.316907-8-sashal@kernel.org> (raw)
In-Reply-To: <20220808013943.316907-1-sashal@kernel.org>

From: Manyi Li <limanyi@uniontech.com>

[ Upstream commit 4b7ef7b05afcde44142225c184bf43a0cd9e2178 ]

[821d6f0359b0614792ab8e2fb93b503e25a65079] is to make machines
produced from 2012 to now not saving NVS region to accelerate S3.

But, Lenovo G40-45, a platform released in 2015, still needs NVS memory
saving during S3. A quirk is introduced for this platform.

Signed-off-by: Manyi Li <limanyi@uniontech.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 drivers/acpi/sleep.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/acpi/sleep.c b/drivers/acpi/sleep.c
index 7a0af16f86f2..d341908cbd16 100644
--- a/drivers/acpi/sleep.c
+++ b/drivers/acpi/sleep.c
@@ -359,6 +359,14 @@ static const struct dmi_system_id acpisleep_dmi_table[] __initconst = {
 		DMI_MATCH(DMI_PRODUCT_NAME, "80E3"),
 		},
 	},
+	{
+	.callback = init_nvs_save_s3,
+	.ident = "Lenovo G40-45",
+	.matches = {
+		DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+		DMI_MATCH(DMI_PRODUCT_NAME, "80E1"),
+		},
+	},
 	/*
 	 * https://bugzilla.kernel.org/show_bug.cgi?id=196907
 	 * Some Dell XPS13 9360 cannot do suspend-to-idle using the Low Power
-- 
2.35.1


  parent reply	other threads:[~2022-08-08  2:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  1:39 [PATCH AUTOSEL 4.14 01/12] arm64: Do not forget syscall when starting a new thread Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 02/12] arm64: fix oops in concurrently setting insn_emulation sysctls Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 03/12] ext2: Add more validity checks for inode counts Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 04/12] genirq: GENERIC_IRQ_IPI depends on SMP Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 05/12] ARM: dts: imx6ul: add missing properties for sram Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 06/12] ARM: dts: imx6ul: fix qspi node compatible Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 07/12] ARM: OMAP2+: display: Fix refcount leak bug Sasha Levin
2022-08-08  1:39 ` Sasha Levin [this message]
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 09/12] ACPI: LPSS: Fix missing check in register_device_clock() Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 10/12] hwmon: (sht15) Fix wrong assumptions in device remove callback Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 11/12] PM: hibernate: defer device probing when resuming from hibernation Sasha Levin
2022-08-08  1:39 ` [PATCH AUTOSEL 4.14 12/12] selinux: Add boundary check in put_entry() Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220808013943.316907-8-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=limanyi@uniontech.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox