> -----Original Message----- > From: Arnd Bergmann [mailto:arnd@xxxxxxxx] > Sent: Friday, February 18, 2011 1:31 AM > To: Guan Xuetao > Cc: linux-kernel@xxxxxxxxxxxxxxx; linux-arch@xxxxxxxxxxxxxxx; 'Greg KH' > Subject: Re: [PATCHv2 09/11] unicore32 core architecture: timer and time handling > > On Sunday 13 February 2011, Guan Xuetao wrote: > > > diff --git a/arch/unicore32/include/asm/timex.h b/arch/unicore32/include/asm/timex.h > > new file mode 100644 > > index 0000000..faf16ba > > --- /dev/null > > +++ b/arch/unicore32/include/asm/timex.h > > +#ifndef __UNICORE_TIMEX_H__ > > +#define __UNICORE_TIMEX_H__ > > + > > +#ifdef CONFIG_ARCH_FPGA > > + > > +/* in FPGA, APB clock is 33M, and OST clock is 32K, */ > > +/* so, 1M is selected for timer interrupt correctly */ > > +#define CLOCK_TICK_RATE (32*1024) > > + > > +#endif > > + > > +#if defined(CONFIG_PUV3_DB0913) \ > > + || defined(CONFIG_PUV3_NB0916) \ > > + || defined(CONFIG_PUV3_SMW0919) > > + > > +#define CLOCK_TICK_RATE (14318000) > > + > > +#endif > > I believe that we don't use CLOCK_TICK_RATE in the kernel any more, > so there is no reason to define it. CLOCK_TICK_RATE is an important value for the kernel. And perhaps I misunderstanding your meaning... > > Arnd Thanks & Regards. Guan Xuetao -- 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