Date: Thu, 9 Feb 2012 06:12:18 +0100
From: Richard Cochran <richardcochran@gmail.com>
To: Dmitry Antipov <dmitry.antipov@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, John Stultz <john.stultz@linaro.org>,
        linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org
Subject: Re: clock_getres() and real resolution
Message-ID: <20120209051218.GC2211@netboy.at.omicron.at>
References: <4F32A347.4090703@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F32A347.4090703@linaro.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 763
Lines: 16

On Wed, Feb 08, 2012 at 08:31:03AM -0800, Dmitry Antipov wrote:
> IIUC, an idea behind clock_getres() is to give a hint about the resolution of
> specified clock. This hint may be used by an application programmer to check whether
> this clock is suitable for a some purpose. So why clock_getres() always returns
> something like {0, 1} (if hrtimers are enabled) regardless of the underlying platform's
> real numbers?

I think "resolution" does not mean tick duration, but rather the finest timer unit.

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