From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: <linux-kernel@vger.kernel.org>
Cc: <torvalds@osdl.org>, "Nakajima, Jun" <jun.nakajima@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>
Subject: [PATCH][2.6][1/5]Support for HPET based timer
Date: Tue, 19 Aug 2003 18:19:19 -0700 [thread overview]
Message-ID: <C8C38546F90ABF408A5961FC01FDBF1902C7D1CC@fmsmsx405.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
[Resend - The original mail hasn't yet appeared on lkml, even 5 hours
after posting]
diff -purN linux-2.6.0-test1/arch/i386/kernel/acpi/boot.c linux-2.6.0-test1-hpet/arch/i386/kernel/acpi/boot.c
--- linux-2.6.0-test1/arch/i386/kernel/acpi/boot.c 2003-07-13 20:37:31.000000000 -0700
+++ linux-2.6.0-test1-hpet/arch/i386/kernel/acpi/boot.c 2003-08-18 19:54:47.000000000 -0700
@@ -289,6 +289,27 @@ acpi_find_rsdp (void)
return rsdp_phys;
}
+#ifdef CONFIG_HPET_TIMER
+extern unsigned long hpet_address;
+
+static int __init acpi_parse_hpet(unsigned long phys, unsigned long size)
+{
+ struct acpi_table_hpet *hpet_tbl;
+
+ hpet_tbl = __va(phys);
+
+ if (hpet_tbl->addr.space_id != ACPI_SPACE_MEM) {
+ printk(KERN_WARNING "acpi: HPET timers must be located in "
+ "memory.\n");
+ return -1;
+ }
+
+ hpet_address = hpet_tbl->addr.addrl;
+ printk(KERN_INFO "acpi: HPET id: %#x base: %#lx\n", hpet_tbl->id,
+ hpet_address);
+ return 0;
+}
+#endif
int __init
acpi_boot_init (void)
@@ -426,6 +447,12 @@ acpi_boot_init (void)
clustered_apic_check();
}
#endif
+#ifdef CONFIG_HPET_TIMER
+ acpi_table_parse(ACPI_HPET, acpi_parse_hpet);
+ if (hpet_address == 0) {
+ printk("ACPI: no HPET table found\n");
+ }
+#endif
return 0;
}
[-- Attachment #2: hpet1.ZIP --]
[-- Type: application/x-zip-compressed, Size: 685 bytes --]
reply other threads:[~2003-08-20 1:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=C8C38546F90ABF408A5961FC01FDBF1902C7D1CC@fmsmsx405.fm.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®