mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Jesse Barnes <jbarnes@engr.sgi.com>,
	linux-kernel@vger.kernel.org, Bob Picco <Robert.Picco@hp.com>,
	venkatesh.pallipadi@intel.com, Andrew Morton <akpm@osdl.org>
Subject: Re: device driver for the SGI system clock, mmtimer
Date: Mon, 20 Sep 2004 15:53:29 -0600	[thread overview]
Message-ID: <200409201553.29824.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409161142570.7453@schroedinger.engr.sgi.com>

On Thursday 16 September 2004 12:46 pm, Christoph Lameter wrote:
> On Thu, 16 Sep 2004, Vojtech Pavlik wrote:
> > mmtimer and hpet are the same hardware actually, just a different
> > specification revision, hpet being the newer one.
> 
> Its basically the same software API but different hardware.

OK, I guess I'm convinced that the SGI mmtimer and the HPET
really are different things.  It looks like the counter resolution,
frequency, and size (which are all described in the HPET register
set) are either compiled into mmtimer or discovered via special-
purpose SGI hooks.

So maybe it's not really a good thing to integrate mmtimer and
hpet.  Apps that mmap the HPET will be expecting a certain register
layout that mmtimer doesn't support.

I was confused because your mmtimer patch mentions the Intel
spec, and the driver identifies itself as "IA-PC Multimedia Timer".
My vote would be to leave mmtimer alone, and perhaps remove the
references to the Intel spec and change the driver ident string.
After all, it doesn't really implement very much of the HPET
functionality, and I don't think the Intel spec says anything
that relates to the SGI hardware.

  reply	other threads:[~2004-09-20 21:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 16:03 Bjorn Helgaas
2004-09-16 16:09 ` Jesse Barnes
2004-09-16 15:52   ` Alan Cox
2004-09-16 17:07     ` Jesse Barnes
2004-09-16 18:17       ` Robert Picco
2004-09-16 18:23         ` Jesse Barnes
2004-09-16 18:00     ` Robert Picco
2004-09-16 16:29   ` Marcello Barnaba
2004-09-16 16:30   ` Christoph Lameter
2004-09-16 18:14   ` Vojtech Pavlik
2004-09-16 18:35     ` Jesse Barnes
2004-09-16 20:34       ` Vojtech Pavlik
2004-09-16 18:46     ` Christoph Lameter
2004-09-20 21:53       ` Bjorn Helgaas [this message]
2004-09-16 16:32 ` Christoph Lameter
2004-09-16 16:54   ` Bjorn Helgaas
2004-09-16 18:07     ` Robert Picco
2004-09-16 20:05       ` Christoph Lameter
2004-09-17  1:34         ` Robert Picco
2004-09-16 18:17     ` Vojtech Pavlik
     [not found] <Pine.LNX.4.58.0409082058140.28678@schroedinger.engr.sgi.com>
     [not found] ` <20040908210537.585120c1.akpm@osdl.org>
2004-09-09  5:12   ` Christoph Lameter
2004-09-09  6:43     ` Jesse Barnes
2004-09-10 19:54       ` Christoph Lameter
2004-09-11 10:50         ` Christoph Hellwig
2004-09-11 15:32           ` Christoph Lameter

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=200409201553.29824.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=Robert.Picco@hp.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=vojtech@suse.cz \
    /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

all inboxes | Powered by JetHome®