From: Gayatri Kammela <gayatri.kammela@intel.com>
To: linux-pm@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, lenb@kernel.org,
dvhart@infradead.org, alex.hung@canonical.com,
rui.zhang@intel.com, daniel.lezcano@linaro.org,
amit.kucheria@verdurent.com, mika.westerberg@intel.com,
peterz@infradead.org, charles.d.prestopine@intel.com,
Gayatri Kammela <gayatri.kammela@intel.com>,
"5 . 6+" <stable@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@intel.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: [PATCH v2 2/3] platform/x86: intel-hid: fix: Update Tiger Lake ACPI device ID
Date: Fri, 27 Mar 2020 14:28:20 -0700 [thread overview]
Message-ID: <4c2882dd12d0b3103b89c3ffd2cbee42aa22dd2d.1585343507.git.gayatri.kammela@intel.com> (raw)
In-Reply-To: <cover.1585343507.git.gayatri.kammela@intel.com>
In-Reply-To: <cover.1585343507.git.gayatri.kammela@intel.com>
Tiger Lake's new unique ACPI device IDs for intel-hid driver is not
valid because of missing 'C' in the ID. Fix the ID by updating it.
After the update, the new ID should now look like
INT1051 --> INTC1051
Fixes: bdd11b654035 ("platform/x86: intel-hid: Add Tiger Lake ACPI device ID")
Cc: 5.6+ <stable@vger.kernel.org> # 5.6+
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Srinivas Pandruvada <srinivas.pandruvada@intel.com>
Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Suggested-by: Srinivas Pandruvada <srinivas.pandruvada@intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
---
drivers/platform/x86/intel-hid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/x86/intel-hid.c b/drivers/platform/x86/intel-hid.c
index 43d590250228..c0a4696803eb 100644
--- a/drivers/platform/x86/intel-hid.c
+++ b/drivers/platform/x86/intel-hid.c
@@ -19,7 +19,7 @@ MODULE_LICENSE("GPL");
MODULE_AUTHOR("Alex Hung");
static const struct acpi_device_id intel_hid_ids[] = {
- {"INT1051", 0},
+ {"INTC1051", 0},
{"INT33D5", 0},
{"", 0},
};
--
2.17.1
next prev parent reply other threads:[~2020-03-27 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 21:28 [PATCH v2 0/3] Fixes: update Tiger Lake ACPI device IDs Gayatri Kammela
2020-03-27 21:28 ` [PATCH v2 1/3] ACPI: fix: Update " Gayatri Kammela
2020-03-30 16:43 ` Rafael J. Wysocki
2020-03-30 17:24 ` Andy Shevchenko
2020-03-30 23:22 ` Kammela, Gayatri
2020-03-31 6:19 ` Rafael J. Wysocki
2020-04-01 11:29 ` Rafael J. Wysocki
2020-03-27 21:28 ` Gayatri Kammela [this message]
2020-03-27 21:28 ` [PATCH v2 3/3] thermal: int340x_thermal: " Gayatri Kammela
2020-03-31 2:38 ` Zhang Rui
2020-03-28 20:43 ` [PATCH v2 0/3] Fixes: update " Andy Shevchenko
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=4c2882dd12d0b3103b89c3ffd2cbee42aa22dd2d.1585343507.git.gayatri.kammela@intel.com \
--to=gayatri.kammela@intel.com \
--cc=alex.hung@canonical.com \
--cc=amit.kucheria@verdurent.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=charles.d.prestopine@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=dvhart@infradead.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).