Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Laird <danieljlaird@hotmail.com>
To: linux-mips@linux-mips.org
Subject: Re: 2.6.19 timer API changes
Date: Wed, 20 Dec 2006 07:48:42 -0800 (PST)	[thread overview]
Message-ID: <7992312.post@talk.nabble.com> (raw)
In-Reply-To: <20061221.004017.21363332.anemo@mba.ocn.ne.jp>




Atsushi Nemoto wrote:
> 
> On Wed, 20 Dec 2006 17:29:25 +0300, Sergei Shtylyov
> <sshtylyov@ru.mvista.com> wrote:
>> > How about this?  You should still fix pnx8550_hpt_read() anyway, but I
>> > suppose gettimeofday() on PNX8550 was broken long time.
>> 
>>     And nobody noticed. :-)
> 
> I changed my mind a bit.  The pre-clocksource gettimeofday() might
> work well on PNX8550.  There was timerlo variable which hold COUNT
> value on last timer interrupt and fixed_gettimeoffset() subtracted
> timerlo from COUNT value at the time.
> 
> On Wed, 20 Dec 2006 17:29:25 +0300, Sergei Shtylyov
> <sshtylyov@ru.mvista.com> wrote:
> 
>> > +static cycle_t pnx8550_hpt_read(void)
>> > +{
>> > +	/* FIXME: we should use timer2 or timer3 as freerun counter */
>> > +	return read_c0_count();
>>  > +}
>> 
>>     I'd suggest read_c0_count2() here, possibly adding an interrupt
>> handler for it since it will interrupt upon hitting compare2
>> reg. value (but we could probably just mask the IRQ off), and
>> enabling the timer 2, of course (the current code disables it)...
> 
> It would be right direction.  And we should set set count2 frequency
> to mips_hpt_frequency.  But I cannot test it by myself so I'd like to
> leave it for others.  Good exercise ;)
> 
> ---
> Atsushi Nemoto
> 
> 
> 
It seems likely that this did work in previous releases, however it will
obviously need to work on this release and so once I have solved the startup
issues by using your second proposed patch I will do some testing to see if
I can get this to work (if it is indeed broken)
Cheers
Dan
-- 
View this message in context: http://www.nabble.com/2.6.19-timer-API-changes-tf2838715.html#a7992312
Sent from the linux-mips main mailing list archive at Nabble.com.

  reply	other threads:[~2006-12-20 15:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  9:15 2.6.19 timer API changes Daniel Laird
2006-12-19  8:17 ` Daniel Laird
2006-12-19 14:34   ` Atsushi Nemoto
2006-12-19 14:51     ` Daniel Laird
2006-12-19 16:23       ` Sergei Shtylyov
2006-12-19 15:01     ` Atsushi Nemoto
2006-12-19 15:34       ` Daniel Laird
2006-12-19 17:15         ` Atsushi Nemoto
2006-12-20  9:37           ` Daniel Laird
2006-12-20 14:12             ` Sergei Shtylyov
2006-12-20 14:50               ` Kevin D. Kissell
2006-12-20 14:50                 ` Kevin D. Kissell
2006-12-20 18:01                 ` Sergei Shtylyov
2006-12-20 15:24             ` Atsushi Nemoto
2006-12-20 15:46               ` Daniel Laird
2006-12-20 14:29           ` Sergei Shtylyov
2006-12-20 15:40             ` Atsushi Nemoto
2006-12-20 15:48               ` Daniel Laird [this message]
2006-12-20 15:48             ` Sergei Shtylyov
2006-12-19 15:52     ` Sergei Shtylyov
2006-12-19 16:29       ` Atsushi Nemoto

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=7992312.post@talk.nabble.com \
    --to=danieljlaird@hotmail.com \
    --cc=linux-mips@linux-mips.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox