x86: HPET: read from HPET_Tn_CMP() not HPET_T0_CMP

In hpet_next_event() we check that the value we just wrote to
HPET_Tn_CMP(timer) has reached the chip. Currently, we're checking that
the value we wrote to HPET_Tn_CMP(timer) is in HPET_T0_CMP, which, if
timer is anything other than timer 0, is likely to fail.

Signed-off-by: Matt Fleming <mjf@gentoo.org>
Cc: mingo@elte.hu
Cc: venkatesh.pallipadi@intel.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

authored by

Matt Fleming and committed by
Thomas Gleixner
89d77a1e 1de5b085

+1 -1
+1 -1
arch/x86/kernel/hpet.c
··· 322 322 * what we wrote hit the chip before we compare it to the 323 323 * counter. 324 324 */ 325 - WARN_ON_ONCE((u32)hpet_readl(HPET_T0_CMP) != cnt); 325 + WARN_ON_ONCE((u32)hpet_readl(HPET_Tn_CMP(timer)) != cnt); 326 326 327 327 return (s32)((u32)hpet_readl(HPET_COUNTER) - cnt) >= 0 ? -ETIME : 0; 328 328 }