linux-kernel - Re: [PATCHv2 09/11] unicore32 core architecture: timer and time handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201102171831.16713.arnd@arndb.de>
Date:	Thu, 17 Feb 2011 18:31:16 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	"Guan Xuetao" <gxt@...c.pku.edu.cn>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	"'Greg KH'" <greg@...ah.com>
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.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/