The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: dsaxena@plexity.net
Cc: mingo@elte.hu, tglx@linutronix.de, dwalker@mvista.com,
	james.perkins@windriver.com, linux-kernel@vger.kernel.org,
	rmk@arm.linux.org.uk, khilman@mvista.com
Subject: Re: [patch-rt 0/2] Initial ARM generic-timeofday support
Date: Mon, 05 Jun 2006 16:16:26 -0700	[thread overview]
Message-ID: <1149549387.11470.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20060605231336.GA11790@plexity.net>

On Mon, 2006-06-05 at 16:13 -0700, Deepak Saxena wrote:
> On Jun 05 2006, at 16:06, john stultz was caught saying:
> > On Mon, 2006-06-05 at 15:29 -0700, dsaxena@plexity.net wrote:
> > > Hi,
> > > 
> > > This patchset (against -rt26, but should apply to newer patch) adds
> > > initial support for generic TOD on ARM. It is fairly simple and
> > > copletely rips out the existing TOD code in ARM, assuming that each
> > > sub-arch will either provide a clocksource or enable CONFIG_IS_TICK_BASED.
> > > Currently only Versatile is supported.
> > 
> > Ah! Looks cool! As a warning, -rt is still running w/ an older version
> > of the TOD code (B20), so some changes will be needed when -rt moves to
> > the current version (C2, right now).
> > 
> > The main change is that the read/sync persistent clock bits got cut, so
> > the clock syncing is still necessary in timer_tick(). There might be a
> > few other differences but most of the changes were arch-generic so it
> > shouldn't be too much of an issue.
> 
> OK, I'll keep my out for that. Actually, maybe I should send you a patch
> for latest TOD code. Are there any plans to just sync the persistent
> time updates with the generic RTC layer? It would require moving stuff
> like the CMOS clock code to drivers/rtc, but it would provide a generic
> solution.

Hmmmm. I like that idea! I've been a bit too busy to look at the RTC
changes in detail, but yes, it sounds like the way to go.

thanks!
-john


  reply	other threads:[~2006-06-05 23:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 22:29 [patch-rt 0/2] Initial ARM generic-timeofday support dsaxena
2006-06-05 22:29 ` [patch-rt 1/2] Remove existing time code from ARM architecture dsaxena
2006-06-05 23:13   ` john stultz
2006-06-05 22:29 ` [patch-rt 2/2] Add clocksource driver for Versatile board dsaxena
2006-06-05 23:17   ` john stultz
2006-06-05 23:06 ` [patch-rt 0/2] Initial ARM generic-timeofday support john stultz
2006-06-05 23:13   ` Deepak Saxena
2006-06-05 23:16     ` john stultz [this message]
2006-06-06 20:05 ` Kevin Hilman

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=1149549387.11470.23.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=dsaxena@plexity.net \
    --cc=dwalker@mvista.com \
    --cc=james.perkins@windriver.com \
    --cc=khilman@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rmk@arm.linux.org.uk \
    --cc=tglx@linutronix.de \
    /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