From: Pavel Machek <pavel@ucw.cz>
To: Len Brown <lenb@kernel.org>
Cc: Len Brown <len.brown@intel.com>, linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH 5/5] intel_idle: do not use the LAPIC timer for ATOM C2
Date: Tue, 2 Nov 2010 02:21:09 +0100 [thread overview]
Message-ID: <20101102011956.GA2648@ucw.cz> (raw)
In-Reply-To: <c25d29952b2a8c9aaf00e081c9162a0e383030cd.1288127069.git.len.brown@intel.com>
On Tue 2010-10-26 17:07:34, Len Brown wrote:
> From: Len Brown <len.brown@intel.com>
>
> If we use the LAPIC timer during ATOM C2 on
> some nvidia chisets, the system stalls.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=21032
> @@ -302,7 +302,7 @@ static int intel_idle_probe(void)
>
> case 0x1C: /* 28 - Atom Processor */
> case 0x26: /* 38 - Lincroft Atom Processor */
> - lapic_timer_reliable_states = (1 << 2) | (1 << 1); /* C2, C1 */
> + lapic_timer_reliable_states = (1 << 1); /* C1 */
> cpuidle_state_table = atom_cstates;
That comment should probably go here, along with list of chipsets.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-11-02 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 21:07 idle patches for 2.6.37 Len Brown
2010-10-26 21:07 ` [PATCH 1/5] intel_idle: simplify test for leave_mm() Len Brown
2010-10-26 21:07 ` [PATCH 2/5] intel_idle: delete bogus data from cpuidle_state.power_usage Len Brown
2010-10-26 21:07 ` [PATCH 3/5] acpi_idle: " Len Brown
2010-10-26 21:07 ` [PATCH 4/5] intel_idle: add initial Sandy Bridge support Len Brown
2010-10-26 21:07 ` [PATCH 5/5] intel_idle: do not use the LAPIC timer for ATOM C2 Len Brown
2010-11-02 1:21 ` Pavel Machek [this message]
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=20101102011956.GA2648@ucw.cz \
--to=pavel@ucw.cz \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-pm@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.