public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <castet.matthieu@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] make pit clocksource continuous
Date: Sun, 13 May 2007 17:55:45 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.05.13.17.55.45@free.fr> (raw)
In-Reply-To: 1179077772.22481.279.camel@localhost.localdomain

Hi,

On Sun, 13 May 2007 19:36:12 +0200, Thomas Gleixner wrote:

> On Sun, 2007-05-13 at 21:23 +0400, Stas Sergeev wrote:
>> Hello.
>> 
>> Thomas Gleixner wrote:
>> >> Does this mean that on even an older
>> >> boards (without acpi at all) the hrtimers won't work?
>> > Not if PIT is the only clocksource available.
>> So you mean it can work without both the pm_timer and hpet? Sorry for
>> bothering you too much, but I am trying to use the hrtimers in my
>> driver module, so I'd like to know all the corner-cases.
> 
> It does _NOT_ work without pm_timer or hpet for the reasons explained
> before.
there something I don't understand : "pm_timer or hpet" aren't 
clockevent ?

Without acpi there should be still pit and tsc as clocksource ?

Also while talking about clockevent why rtc couldn't be used for that ?


Thanks

Matthieu


  reply	other threads:[~2007-05-13 17:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 23:18 [patch] make pit clocksource continuous Stas Sergeev
2007-05-12 23:38 ` Daniel Walker
2007-05-13  7:16 ` Thomas Gleixner
2007-05-13  9:04   ` Stas Sergeev
2007-05-13 14:54     ` Thomas Gleixner
2007-05-13 16:48       ` Stas Sergeev
2007-05-13 16:50         ` Thomas Gleixner
2007-05-13 17:23           ` Stas Sergeev
2007-05-13 17:36             ` Thomas Gleixner
2007-05-13 17:55               ` Matthieu CASTET [this message]
2007-05-13 18:17               ` Stas Sergeev

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=pan.2007.05.13.17.55.45@free.fr \
    --to=castet.matthieu@free.fr \
    --cc=linux-kernel@vger.kernel.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