/linux/arch/x86/kernel/ |
H A D | hpet.c | 6 #include <linux/hpet.h> 12 #include <asm/hpet.h> 17 #define pr_fmt(fmt) "hpet: " fmt 50 * HPET address is set in acpi/boot.c, when an ACPI entry exists 100 * HPET command line enable / disable 119 __setup("hpet=", hpet_setup); 134 * is_hpet_enabled - Check whether the legacy HPET timer interrupt is enabled 184 * When the HPET driver (/dev/hpet) is enabled, we need to reserve 235 /* Associate the first unused channel to /dev/hpet */ in hpet_select_device_channel() 248 /* Common HPET functions */ [all …]
|
H A D | quirks.c | 9 #include <asm/hpet.h> 85 /* HPET disabled in HPTC. Trying to enable */ in ich_force_hpet_resume() 93 printk(KERN_DEBUG "Force enabled HPET at resume\n"); in ich_force_hpet_resume() 109 "cannot force enable HPET\n"); in ich_force_enable_hpet() 117 "cannot force enable HPET\n"); in ich_force_enable_hpet() 125 /* HPET is enabled in HPTC. Just not reported by BIOS */ in ich_force_enable_hpet() 128 dev_printk(KERN_DEBUG, &dev->dev, "Force enabled HPET at " in ich_force_enable_hpet() 134 /* HPET disabled in HPTC. Trying to enable */ in ich_force_enable_hpet() 149 "Failed to force enable HPET\n"); in ich_force_enable_hpet() 152 dev_printk(KERN_DEBUG, &dev->dev, "Force enabled HPET at " in ich_force_enable_hpet() [all …]
|
H A D | time.c | 25 #include <asm/hpet.h> 35 * Default timer interrupt handler for PIT/HPET 70 * Before PIT/HPET init, select the interrupt mode. This is required in x86_late_time_init() 79 * After PIT/HPET timers init, set up the final interrupt mode for in x86_late_time_init()
|
H A D | i8253.c | 13 #include <asm/hpet.h> 18 * HPET replaces the PIT, when enabled. So we need to know, which of 64 * - when HPET is enabled in init_pit_clocksource()
|
H A D | devicetree.c | 22 #include <asm/hpet.h> 116 dn = of_find_compatible_node(NULL, NULL, "intel,ce4100-hpet"); in dtb_setup_hpet()
|
H A D | tsc_msr.c | 220 * Another fact is that on MSR capable platforms, PIT/HPET is in cpu_khz_from_msr() 229 * reliable clocksource on these SoCs (HPET is either not present in cpu_khz_from_msr()
|
/linux/Documentation/timers/ |
H A D | hpet.rst | 5 The High Precision Event Timer (HPET) hardware follows a specification 8 Each HPET has one fixed-rate counter (at 10+ MHz, hence "High Precision") 15 HPET devices can support two interrupt routing modes. In one mode, the 17 role. Many x86 BIOS writers don't route HPET interrupts at all, which 22 The driver supports detection of HPET driver allocation and initialization 23 of the HPET before the driver module_init routine is called. This enables 24 platform code which uses timer 0 or 1 as the main timer to intercept HPET 26 arch/x86/kernel/hpet.c.
|
/linux/arch/mips/loongson64/ |
H A D | hpet.c | 9 #include <asm/hpet.h> 191 * hpet address assignation and irq setting should be done in bios. 207 /* set hpet base address */ in hpet_setup() 210 /* enable decoding of access to HPET MMIO*/ in hpet_setup() 213 /* HPET irq enable */ in hpet_setup() 228 cd->name = "hpet"; in setup_hpet_timer() 245 if (request_irq(HPET_T0_IRQ, hpet_irq_handler, flags, "hpet", NULL)) in setup_hpet_timer() 246 pr_err("Failed to request irq %d (hpet)\n", HPET_T0_IRQ); in setup_hpet_timer() 247 pr_info("hpet clock event device register\n"); in setup_hpet_timer() 266 .name = "hpet", [all …]
|
H A D | Kconfig | 5 bool "RS780/SBX00 HPET Timer" 10 This option enables the hpet timer of AMD RS780/SBX00.
|
H A D | Makefile | 10 obj-$(CONFIG_RS780_HPET) += hpet.o
|
H A D | time.c | 11 #include <asm/hpet.h>
|
/linux/include/linux/ |
H A D | hpet.h | 5 #include <uapi/linux/hpet.h> 9 * Offsets into HPET Registers 12 struct hpet { struct 43 * HPET general capabilities register 56 * HPET general configuration register
|
/linux/arch/x86/include/asm/ |
H A D | hpet.h | 56 /* Max HPET Period is 10^8 femto sec as in HPET spec */ 59 * Min HPET period is 10^5 femto sec just for safety. If it is less than this, 60 * then 32 bit HPET counter wrapsaround in less than 0.5 sec. 64 /* hpet memory map physical address */
|
/linux/arch/mips/include/asm/ |
H A D | hpet.h | 58 /* Max HPET Period is 10^8 femto sec as in HPET spec */ 61 * Min HPET period is 10^5 femto sec just for safety. If it is less than this, 62 * then 32 bit HPET counter wrapsaround in less than 0.5 sec.
|
/linux/Documentation/devicetree/bindings/x86/ |
H A D | timer.txt | 4 * High Precision Event Timer (HPET) 6 compatible = "intel,ce4100-hpet";
|
H A D | ce4100.txt | 6 Many of the "generic" devices like HPET or IO APIC have the ce4100
|
/linux/Documentation/virt/kvm/x86/ |
H A D | timekeeping.rst | 195 system chipset, sometimes by an HPET and some frankenstein IRQ routing. 291 2.4. HPET 294 HPET is quite complex, and was originally intended to replace the PIT / RTC 297 systems designated as legacy free may support only the HPET as a hardware timer 300 The HPET spec is rather loose and vague, requiring at least 3 hardware timers, 305 In general, the HPET is recommended as a high precision (compared to PIT /RTC) 306 time source which is independent of local variation (as there is only one HPET 307 in any given system). The HPET is also memory-mapped, and its presence is 310 Detailed specification of the HPET is beyond the current scope of this 588 An additional concern is that timers based off the TSC (or HPET, if the raw bus
|
/linux/arch/x86/kernel/acpi/ |
H A D | boot.c | 886 #include <asm/hpet.h> 895 pr_warn("HPET timers must be located in memory.\n"); in acpi_parse_hpet() 903 * Some broken BIOSes advertise HPET at 0x0. We really do not in acpi_parse_hpet() 907 pr_warn("HPET id: %#x base: %#lx is invalid\n", hpet_tbl->id, hpet_address); in acpi_parse_hpet() 912 * Some even more broken BIOSes advertise HPET at in acpi_parse_hpet() 918 …pr_warn("HPET id: %#x base: 0xfed0000000000000 is bogus, try hpet=force on the kernel command line… in acpi_parse_hpet() 923 pr_warn("HPET id: %#x base: 0xfed0000000000000 fixed up to 0xfed00000.\n", in acpi_parse_hpet() 928 pr_info("HPET id: %#x base: %#lx\n", hpet_tbl->id, hpet_address); in acpi_parse_hpet() 931 * Allocate and initialize the HPET firmware resource for adding into in acpi_parse_hpet() 940 snprintf((char *)hpet_res->name, HPET_RESOURCE_NAME_SIZE, "HPET %u", in acpi_parse_hpet() [all …]
|
/linux/drivers/rtc/ |
H A D | rtc-cmos.c | 51 * Use ACPI SCI to replace HPET interrupt for RTC Alarm event 117 * HPET #1 hijacking the IRQ for this RTC, and being unavailable for 121 * emulation of hardware RTC IRQ facilities using HPET #1. We don't 122 * want to use HPET for anything except those IRQs though... 125 #include <asm/hpet.h> 173 /* Don't use HPET for RTC Alarm event if ACPI Fixed event is used */ 500 * FIXME the HPET alarm glue currently ignores day_alrm in cmos_set_alarm_callback() 698 /* When the HPET interrupt handler calls us, the interrupt in cmos_interrupt() 700 * always clear irq status, even when HPET is in the way. in cmos_interrupt() 702 * Note that HPET and RTC are almost certainly out of phase, in cmos_interrupt() [all …]
|
/linux/samples/timers/ |
H A D | hpet_example.c | 16 #include <linux/hpet.h> 59 fprintf(stderr, "-hpet: requires command\n"); in main() 68 fprintf(stderr, "-hpet: executing %s\n", in main()
|
/linux/Documentation/core-api/ |
H A D | printk-index.rst | 52 <6> arch/x86/kernel/hpet.c:144 _hpet_print_config "hpet: %s(%d):\n"
|
/linux/arch/mips/loongson2ef/common/ |
H A D | time.c | 11 #include <asm/hpet.h>
|
/linux/include/uapi/linux/ |
H A D | hpet.h | 24 #define MAX_HPET_TBS 8 /* maximum hpet timer blocks */
|
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | intel,ce4100-ioapic.yaml | 22 Many of the Intel's generic devices like hpet, ioapic, lapic have
|
/linux/drivers/char/ |
H A D | Makefile | 21 obj-$(CONFIG_HPET) += hpet.o
|