mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@intel.com>
To: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, len.brown@intel.com,
	john.stultz@linaro.org
Cc: matthew.lee@intel.com, Feng Tang <feng.tang@intel.com>
Subject: [PATCH] x86/intel: Add comments about why we disabled HPET on Baytrail
Date: Mon, 15 Jun 2015 17:40:01 +0800	[thread overview]
Message-ID: <1434361201-31743-1-git-send-email-feng.tang@intel.com> (raw)

The question has been asked many times, and finally I found the
official document which explains the problem of HPET on Baytrail
that it will halt in deep idle states.

Signed-off-by: Feng Tang <feng.tang@intel.com>
---
 arch/x86/kernel/early-quirks.c |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
index fe9f0b7..9cdc6acb 100644
--- a/arch/x86/kernel/early-quirks.c
+++ b/arch/x86/kernel/early-quirks.c
@@ -628,7 +628,10 @@ static struct chipset early_qrk[] __initdata = {
 	  QFLAG_APPLY_ONCE, intel_graphics_stolen },
 	/*
 	 * HPET on current version of Baytrail platform has accuracy
-	 * problems, disable it for now:
+	 * problems, that it will halt in deep idle state, so disable it.
+	 *
+	 * Please refer section 18.10.1.3 of http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z8000-datasheet-vol-1.pdf 
+	 * for more details.
 	 */
 	{ PCI_VENDOR_ID_INTEL, 0x0f00,
 		PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
-- 
1.7.9.5


             reply	other threads:[~2015-06-15  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15  9:40 Feng Tang [this message]
2015-06-18 10:54 ` [tip:x86/platform] x86/platform/intel/baytrail: " tip-bot for Feng Tang

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=1434361201-31743-1-git-send-email-feng.tang@intel.com \
    --to=feng.tang@intel.com \
    --cc=hpa@zytor.com \
    --cc=john.stultz@linaro.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.lee@intel.com \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®