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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 1 Sep 2014 10:35:16 +0200 (CEST)
From:	Thomas Gleixner <>
To:	Oleksij Rempel <>
	Daniel Lezcano <>
Subject: Re: Writing clocksource driver, tips?

On Sun, 31 Aug 2014, Oleksij Rempel wrote:
> - 1 timer can be used for clocksource other as  clock_event_device, how
> can i use other 2 timers on same controller. and how can i use other 3
> controllers?

All you need is two.

One for the clocksource (free running counter):

    100MHz is fine, it gives the timekeeping code nice
    granularity. There is no need for a wrap around interrupt. The
    core code knows how to deal with it.

The second one is for the clock event device

    Avoid a match timer if possible, it's a pain in the neck. Either a
    autoreloading timer for the periodic mode or a simple downcounting
    one for one shot mode is good enough.

The other timers are not of any value for Linux. Just leave them


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists