On Tuesday 28 October 2014 10:46:29 Ley Foon Tan wrote: > On Sun, Oct 26, 2014 at 5:10 AM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: > > On Fri, 24 Oct 2014, Ley Foon Tan wrote: > >> +#ifndef _ASM_NIOS2_TIMEX_H > >> +#define _ASM_NIOS2_TIMEX_H > >> + > >> +typedef unsigned long cycles_t; > >> + > >> +extern cycles_t get_cycles(void); > >> + > >> +#define ARCH_HAS_READ_CURRENT_TIMER > > > > Why does NIOS need that? Does it have a hardware implementation > > dependent clock frequency which needs to be calibrated at boot time? > This is suggestion from Arnd to use read_current_timer instead of using > expensive delay loop calibration during boot. My mistake, sorry. I think the right way is to define calibrate_delay_is_known() rather than read_current_timer(), I was getting confused by the ARM implementation that does both. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
