Messages in this thread | | | Date | Mon, 10 Feb 2014 09:46:07 -0800 | From | Sören Brinkmann <> | Subject | Re: [PATCH v3 5/7] clocksource/cadence_ttc: Use only one counter |
| |
Hi Thomas,
On Tue, Feb 04, 2014 at 09:41:53PM +0100, Thomas Gleixner wrote: > On Mon, 3 Feb 2014, Soren Brinkmann wrote: > > > Currently the driver uses two of the three counters the TTC provides to > > implement a clocksource and a clockevent device. By using the TTC's > > match feature we can implement both use cases using a single counter > > only. > > Are you entirely sure that this match feature is free of the infamous > HPET match feature issues? > > See arch/x86/kernel/hpet.c: hpet_next_event() > > If yes, please add a comment. If no .... Good catch. Looks like the comparator compares on == as well. So, I assume it may show similar issues. I'll have to spend some more time looking into this.
Thanks for applying the first two patches of the series.
Thanks, Sören
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |