[lkml]   [2012]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 4/4] hpet: factor timer allocate from open
On Mon, 5 Mar 2012, wrote:

> From: Magnus Lynch <>
> Subject: hpet: factor timer allocate from open
> The current implementation of the /dev/hpet driver couples opening the
> device with allocating one of the (scarce) timers (aka comparators). This
> is a limitation in that the main counter may be valuable to applications
> seeking a high-resolution timer who have no use for the interrupt
> generating functionality of the comparators.
> This patch alters the open semantics so that when the device is opened, no
> timer is allocated. Operations that depend on a timer being in context
> implicitly attempt allocating a timer, to maintain backward compatibility.

AFAICT, there is only fasync which calls hpet_alloc_timer(). All other
functions are broken by this chage.

> There is also an IOCTL (HPET_ALLOC_TIMER _IO) added so that the
> allocation may be done explicitly. (I prefer the explicit open then

And that IOCTL does what? Return 0 is not really useful functionality.



 \ /
  Last update: 2012-03-06 13:55    [W:0.045 / U:1.584 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site