From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i.MX31: document timer precision option
Date: Thu, 18 Sep 2008 18:52:39 +0900 [thread overview]
Message-ID: <48D224E7.5020809@necel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0808281223370.6514@axis700.grange>
Hi Guennadi,
Guennadi Liakhovetski wrote:
> Signed-off-by: Guennadi Liakhovetski <lg@denx.de>
> ---
>
> diff -u /dev/null doc/README.imx31
> --- /dev/null 2008-08-28 10:21:05.503011301 +0200
> +++ doc/README.imx31 2008-08-28 12:15:21.000000000 +0200
> @@ -0,0 +1,13 @@
> +i.MX31 specific Configuration Options:
> +--------------------------------------
> +
> +- Timer precision:
> + CONFIG_MX31_TIMER_HIGH_PRECISION
> +
> + Enable higher precision timer. The low-precision timer
> + (default) provides approximately 4% error, whereas the
> + high-precision timer is about 0.4% accurate. The extra
> + accuracy is achieved at the cost of higher computational
> + overhead, which, in places where time is measured, should
> + not be critical, so, it should be safe to enable this
> + option.
I'm not familiar with the maintainance policy of README and doc/*, but
is there any reasone this README.imx31 is sitting on the top of tree?
Should be marged into $(TOPDIR)/README, or moved to doc/ directory?
Noticed a few minutes ago, so just let you know...
--
Shinya Kuribayashi
NEC Electronics
next prev parent reply other threads:[~2008-09-18 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 10:25 [U-Boot] [PATCH] i.MX31: document timer precision option Guennadi Liakhovetski
2008-09-18 9:52 ` Shinya Kuribayashi [this message]
2008-09-18 12:25 ` Guennadi Liakhovetski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48D224E7.5020809@necel.com \
--to=shinya.kuribayashi@necel.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.