From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
Len Brown <lenb@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, "Van De Ven,
Arjan" <arjan.van.de.ven@intel.com>
Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1]
Date: Tue, 14 Nov 2006 21:30:17 +0100 [thread overview]
Message-ID: <20061114203016.GA15440@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454E0DC9D@scsmsx413.amr.corp.intel.com>
Hi,
On Tue, Nov 14, 2006 at 10:06:37AM -0800, Pallipadi, Venkatesh wrote:
> >Hmm, hopefully it's easy to research where to enable HPET
> >(if there is one at all!) on an el-cheapo VIA chipset...
> >
> >Many thanks for your patch! (even though currently Intel-only)
>
> Yes. This should be easy to do for any chipset. It should be documented
> somewhere in the chipset documentation. Atleast it is documented on ICH
> specification :).
OK, I just managed to get hold of both VT8237 *and* VT8235 specs.
VT8237 is documented to have HPET.
The convenient thing is that on VT8235 *exactly* that register space where
8237 has its HPET is marked as "reserved" ;)
(i.e. there's a register hole which has exactly the size of the
HPET range).
IOW, we might be lucky and 8235 already has an initial implementation of
HPET available (which even works??).
OK, so let's provide some more details:
VT8237 has a PCI device 17 function 0 part ("Bus Control and Power Management")
which has a Programmable Chip Select Control block at 0x5D to 0x6B.
Offset 0x68 is HPET Control, RW, which has an Enable bit (default Disabled)
at bit 7 (MSB).
0x69 to 0x6B is HPET Base Address, RW (lower 22 bits, 22-23 "Reserved").
VT8235 has exactly 0x68 to 0x6B "reserved", with valid registers both
before and thereafter.
There's also some register description about APIC timer,
maybe I'll gather something about my C2 headaches from there.
Andreas Mohr
next prev parent reply other threads:[~2006-11-14 20:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 18:06 Pallipadi, Venkatesh
2006-11-14 20:30 ` Andreas Mohr [this message]
2006-11-14 21:00 ` Andreas Mohr
2006-11-14 21:18 ` Andreas Mohr
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 17:21 Pallipadi, Venkatesh
2006-11-14 17:30 ` Andreas Mohr
2006-11-14 18:04 ` Andreas Mohr
2006-12-17 15:58 ` Tobias Diedrich
2006-11-01 14:07 Andreas Mohr
2006-11-01 21:51 ` Thomas Gleixner
2006-11-02 0:18 ` Andreas Mohr
2006-11-02 7:31 ` Thomas Gleixner
2006-11-02 8:14 ` Thomas Gleixner
2006-11-02 17:22 ` Thomas Gleixner
2006-11-02 19:28 ` Andreas Mohr
2006-11-02 20:34 ` Andreas Mohr
2006-11-03 0:06 ` Andreas Mohr
2006-11-06 16:20 ` Thomas Gleixner
2006-11-06 20:58 ` Andreas Mohr
2006-11-07 6:41 ` Len Brown
2006-11-07 8:07 ` Ingo Molnar
2006-11-07 8:25 ` Thomas Gleixner
2006-11-07 9:16 ` Andreas Mohr
2006-11-07 9:28 ` Thomas Gleixner
2006-11-07 9:45 ` Thomas Gleixner
2006-11-07 22:27 ` Andreas Mohr
2006-11-08 19:36 ` Thomas Gleixner
2006-11-14 6:34 ` Len Brown
2006-11-07 8:18 ` Andreas Mohr
2006-11-07 8:24 ` Ingo Molnar
2006-11-14 6:27 ` Len Brown
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=20061114203016.GA15440@rhlx01.hs-esslingen.de \
--to=andi@rhlx01.fht-esslingen.de \
--cc=arjan.van.de.ven@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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®