From: John Stultz <johnstul@us.ibm.com>
To: wuzhangjin@gmail.com
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
linux-kernel@vger.kernel.org,
Arnaud Patard <apatard@mandriva.com>,
loongson-dev@googlegroups.com, zhangfx@lemote.com,
yanh@lemote.com, Philippe Vachon <philippe@cowpig.ca>,
Zhang Le <r0bertz@gentoo.org>, Erwan Lerale <erwan@thiscow.com>
Subject: Re: [PATCH 23/30] loongson: CS5536 MFGPT as system clock source support
Date: Fri, 15 May 2009 18:23:24 -0700 [thread overview]
Message-ID: <1242437004.29511.202.camel@jstultz-laptop> (raw)
In-Reply-To: <1242436541.10164.194.camel@falcon>
On Sat, 2009-05-16 at 09:15 +0800, Wu Zhangjin wrote:
> On Fri, 2009-05-15 at 17:39 -0700, john stultz wrote:
> > On Fri, May 15, 2009 at 3:23 PM, Wu Zhangjin <wuzhangjin@gmail.com> wrote:
> > > +static struct clocksource clocksource_mfgpt = {
> > > + .name = "mfgpt",
> > > + .rating = 1200,
> >
> > Minor nit. Please read the comment over the struct clocksource
> > definition in include/linux/clocksource.h for a guide to setting the
> > rating value for your clocksource.
> >
>
> as the comment describes, just like the 8253 Timer, the precision of
> cs5536 mfgpt Timer is not good, the rating of it should be in the range
> of 100-199? Functional for real use, but not desired?
That would seem reasonable to me, as it insures that should better
clocksources become available on the hardware, it will pick the better
hardware.
But I'll leave the final call to you.
I just wanted to make sure we're all using the same scale, and 1200 was
off the charts ;)
thanks
-john
prev parent reply other threads:[~2009-05-16 1:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 22:23 [PATCH 23/30] loongson: CS5536 MFGPT as system clock source support Wu Zhangjin
2009-05-15 22:23 ` Wu Zhangjin
2009-05-16 0:39 ` john stultz
2009-05-16 0:39 ` john stultz
2009-05-16 1:15 ` Wu Zhangjin
2009-05-16 1:15 ` Wu Zhangjin
2009-05-16 1:23 ` John Stultz [this message]
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=1242437004.29511.202.camel@jstultz-laptop \
--to=johnstul@us.ibm.com \
--cc=apatard@mandriva.com \
--cc=erwan@thiscow.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=loongson-dev@googlegroups.com \
--cc=philippe@cowpig.ca \
--cc=r0bertz@gentoo.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.com \
--cc=yanh@lemote.com \
--cc=zhangfx@lemote.com \
/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.