Re: [RFC PATCH v2 02/14] x86/hpet: Expose more functions to read and write registers

2019-04-08 Thread Ricardo Neri
On Tue, Mar 26, 2019 at 10:00:24PM +0100, Thomas Gleixner wrote: > On Wed, 27 Feb 2019, Ricardo Neri wrote: > > struct irq_data; > > @@ -109,6 +114,11 @@ extern void > > hpet_unregister_irq_handler(rtc_irq_handler handler); > > static inline int hpet_enable(void) { return 0; } > > static

Re: [RFC PATCH v2 02/14] x86/hpet: Expose more functions to read and write registers

2019-03-26 Thread Thomas Gleixner
On Wed, 27 Feb 2019, Ricardo Neri wrote: > struct irq_data; > @@ -109,6 +114,11 @@ extern void hpet_unregister_irq_handler(rtc_irq_handler > handler); > static inline int hpet_enable(void) { return 0; } > static inline int is_hpet_enabled(void) { return 0; } > #define hpet_readl(a) 0 >

[RFC PATCH v2 02/14] x86/hpet: Expose more functions to read and write registers

2019-02-27 Thread Ricardo Neri
Some of the registers in the HPET hardware have a width of 64 bits. 64-bit access functions are needed mostly to read the counter and write the comparator in a single read or write. Also, 64-bit accesses can be used to to read parameters located in the higher bits of some registers (such as the