From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de
Cc: hpa@zytor.com, harry.pan@intel.com, feng.tang@intel.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: [PATCH 2/2] x86/intel: Disable HPET on Intel Ice Lake platforms
Date: Fri, 29 Nov 2019 14:23:03 +0800 [thread overview]
Message-ID: <20191129062303.18982-2-kai.heng.feng@canonical.com> (raw)
In-Reply-To: <20191129062303.18982-1-kai.heng.feng@canonical.com>
Like CFL and CFL-H, ICL SoC has skewed HPET timer once it hits PC10.
So let's disable HPET on ICL.
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
---
arch/x86/kernel/early-quirks.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
index 606711f5ebf8..2f9ec14be3b1 100644
--- a/arch/x86/kernel/early-quirks.c
+++ b/arch/x86/kernel/early-quirks.c
@@ -714,6 +714,8 @@ static struct chipset early_qrk[] __initdata = {
PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
{ PCI_VENDOR_ID_INTEL, 0x3ec4,
PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
+ { PCI_VENDOR_ID_INTEL, 0x8a12,
+ PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
{ PCI_VENDOR_ID_BROADCOM, 0x4331,
PCI_CLASS_NETWORK_OTHER, PCI_ANY_ID, 0, apple_airport_reset},
{}
--
2.17.1
next prev parent reply other threads:[~2019-11-29 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 6:23 [PATCH 1/2] x86/intel: Disable HPET on Intel Coffee Lake H platforms Kai-Heng Feng
2019-11-29 6:23 ` Kai-Heng Feng [this message]
2019-11-29 11:23 ` [tip: timers/urgent] x86/intel: Disable HPET on Intel Ice Lake platforms tip-bot2 for Kai-Heng Feng
2019-11-29 11:23 ` [tip: timers/urgent] x86/intel: Disable HPET on Intel Coffee Lake H platforms tip-bot2 for Kai-Heng Feng
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=20191129062303.18982-2-kai.heng.feng@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=bp@alien8.de \
--cc=feng.tang@intel.com \
--cc=harry.pan@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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).