All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: plat_timer_setup, mips_timer_ack, etc.
Date: Wed, 17 Oct 2007 17:28:37 +0100	[thread overview]
Message-ID: <20071017162837.GA5491@linux-mips.org> (raw)
In-Reply-To: <20071017.020113.63743059.anemo@mba.ocn.ne.jp>

On Wed, Oct 17, 2007 at 02:01:13AM +0900, Atsushi Nemoto wrote:

> On Tue, 16 Oct 2007 17:36:10 +0100, Ralf Baechle <ralf@linux-mips.org> wrote:
> > > Also I found mips_timer_ack and cycles_per_jiffy are not used now.
> > > Can we remove them entirely?
> > 
> > I think so.  Each clockevent device should rather try to be independent
> > of others.  What made the old timer code such a mess is that it was
> > desparately trying to share resources giving everybody plenty of rope ...
> 
> So all mips_timer_ack users should implement its own clockevent
> device, right?

Yes.

> $ git-grep mips_timer_ack arch/mips
> arch/mips/dec/time.c:   mips_timer_ack = dec_timer_ack;
> arch/mips/jmr3927/rbhma3100/setup.c:    mips_timer_ack = jmr3927_timer_ack;
> arch/mips/philips/pnx8550/common/time.c:        mips_timer_ack = timer_ack;
> arch/mips/sni/time.c:        mips_timer_ack = sni_a20r_timer_ack;

Not too many then I guess ;-)

  Ralf

  reply	other threads:[~2007-10-17 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 15:52 plat_timer_setup, mips_timer_ack, etc Atsushi Nemoto
2007-10-16 16:36 ` Ralf Baechle
2007-10-16 17:01   ` Atsushi Nemoto
2007-10-17 16:28     ` Ralf Baechle [this message]
2007-10-17 16:34       ` Sergei Shtylyov
2007-10-17 16:58         ` Ralf Baechle
2007-10-17 17:40         ` Ralf Baechle

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=20071017162837.GA5491@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --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 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.