mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Weiner <jw@emlix.com>
To: Chris Zankel <chris@zankel.net>
Cc: linux-kernel@vger.kernel.org
Subject: [patch 0/3] xtensa generic time
Date: Tue, 03 Mar 2009 16:30:43 +0100	[thread overview]
Message-ID: <E1LeXCe-0006wA-5k@mailer.emlix.com> (raw)

Hi,

here are three patches that convert the xtensa arch code to make use
of the generic time implementation.

The first one just removes xtensa's sched_clock() in order to use the
default implementation as it is the same thing.

The second one removes the platform-specific rtc get/set callbacks,
the interface is not really feasible for the generic time
implementation.  Currently, no platform implements this callback.
Platforms that want to should implement a rtc driver and
read_persistent_clock().

The third one converts xtensa to use generic time code by implementing
ccount as a clocksource.  This lets us get rid of xtensa-specific
gtod/stod as now the generic time code is used for that.

	Hannes

 arch/xtensa/Kconfig                |    3 +
 arch/xtensa/include/asm/platform.h |   11 ---
 arch/xtensa/kernel/platform.c      |    2 -
 arch/xtensa/kernel/time.c          |  120 +++++-------------------------------
 4 files changed, 19 insertions(+), 117 deletions(-)


             reply	other threads:[~2009-03-03 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 15:30 Johannes Weiner [this message]
2009-03-03 15:30 ` [patch 1/3] xtensa: use generic sched_clock() Johannes Weiner
2009-03-03 15:30 ` [patch 2/3] xtensa: remove platform rtc hooks Johannes Weiner
2009-03-03 15:30 ` [patch 3/3] xtensa: ccount clocksource Johannes Weiner
2009-03-03 17:55   ` Daniel Walker
2009-03-03 19:54     ` Johannes Weiner
2009-03-03 21:36       ` Daniel Walker
2009-03-04 20:26         ` Johannes Weiner

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=E1LeXCe-0006wA-5k@mailer.emlix.com \
    --to=jw@emlix.com \
    --cc=chris@zankel.net \
    --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

all inboxes | Powered by JetHome®