On Wed, May 20, 2015 at 10:53 AM, Harald Geyer <[email protected]> wrote: > Hi John, > > John Stultz writes: >> From: Harald Geyer <[email protected]> >> >> This patch series introduces a new function >> u32 ktime_get_resolution_ns(void) >> which allows to clean up some driver code. > > thanks for keeping track of this, but is this patch still useful? > > I was thinking that the variable hrtimer_resolution, that Thomas > introduced in > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/include/linux/hrtimer.h?h=timers/wip&id=03eeacdb07e2fdfc4ef311c2593286c92eba609c > is meant to provide the same information. I haven't looked into this > in detail yet, so I might be wrong, but it is on my todo list for > after it appears in the trees I work with...
Well, I don't think the above covers the same usage, since one is the hrtimer resolution (which we expose to userspace via the posix timers interface) vs the timekeeping/clocksource resolution (which we don't intend to expose to userspace). That said, if you're not sure if this patch is still necessary, I'm happy to drop it, since your iio code was the only potential user so far. :) thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
