public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: Architecture specific implementations for tickless kernel and deferrable timers
Date: Fri, 29 Apr 2011 19:05:45 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1104291905200.3005@ionos> (raw)
In-Reply-To: <BANLkTimcyE3tG+F1sDiNRr1rGkmdvp_4ig@mail.gmail.com>

On Fri, 29 Apr 2011, Vikram Narayanan wrote:

> On Fri, Apr 29, 2011 at 8:04 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Fri, Apr 29, 2011 at 07:56:56PM +0530, Vikram Narayanan wrote:
> >> Can you also give some idea on how the system's RTC is hooked up with
> >> the generic timekeeping code.
> >> Is it hooked up in someway so that the walltime is calculated wrt the
> >> initial value of the RTC?
> >
> > I'd like to pass you over to the RTC folk, but I don't think they're
> > very active anymore.
> >
> > Suffice it to say that the RTC subsystem will set the system date/time
> > on initialization from the RTC device if one is provided. ?All I can
> > suggest is to look at drivers/rtc and include/linux/rtc.h for the
> > details. ?The MAINTAINERS file should list who is responsible for RTC
> > stuff as well as a mailing list for it.
> >
> Yes. Sure. I already have a driver in place for RTC, under /dev/rtc. I
> will try to post my doubts in the RTC mailing lists.
> Just noticed a folder clocksource under drivers.
> Quite curious about what it is for?
> Can you give some hints about it?

That's for clock sources which are shared accross platforms.

Thanks,

	tglx

  reply	other threads:[~2011-04-29 17:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 18:15 Architecture specific implementations for tickless kernel and deferrable timers Vikram Narayanan
2011-04-22  3:13 ` Jeff Ohlstein
2011-04-24 14:20   ` Vikram Narayanan
2011-04-26 20:37     ` Russell King - ARM Linux
2011-04-27  3:30       ` Vikram Narayanan
2011-04-27  7:25         ` Russell King - ARM Linux
2011-04-27  8:17         ` Thomas Gleixner
2011-04-28 13:31           ` Vikram Narayanan
2011-04-28 13:38             ` Russell King - ARM Linux
2011-04-28 13:54               ` Vikram Narayanan
2011-04-28 14:28                 ` Russell King - ARM Linux
2011-04-28 17:29                   ` Vikram Narayanan
2011-04-28 18:24                     ` Russell King - ARM Linux
2011-04-29 14:26                       ` Vikram Narayanan
2011-04-29 14:34                         ` Russell King - ARM Linux
2011-04-29 15:07                           ` Vikram Narayanan
2011-04-29 17:05                             ` Thomas Gleixner [this message]
2011-04-29 17:05                           ` Thomas Gleixner
2011-04-29 17:57                             ` john stultz
2011-05-03  2:17                               ` Vikram Narayanan

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=alpine.LFD.2.02.1104291905200.3005@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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