From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: move read_{boot,persistent}_clock to the architecture level
Date: Fri, 4 May 2012 17:13:23 -0700 [thread overview]
Message-ID: <20120505001323.GD5613@atomide.com> (raw)
In-Reply-To: <1335617145-24649-1-git-send-email-marc.zyngier@arm.com>
* Marc Zyngier <marc.zyngier@arm.com> [120428 05:49]:
> At the moment, read_persistent_clock is implemented at the
> platform level, which makes it impossible to compile these
> platforms in a single kernel.
>
> Implement these two functions at the architecture level, and
> provide a thin registration interface for both read_boot_clock
> and read_persistent_clock. The two affected platforms (OMAP and
> Tegra) are converted at the same time.
>
> Compile tested only.
Sorry I'm a bit behind with emails again..
Boot tested on omap1 and omap2/3/4:
Tested-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2012-05-05 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 12:45 [PATCH] ARM: move read_{boot, persistent}_clock to the architecture level Marc Zyngier
2012-05-01 18:11 ` Stephen Warren
2012-05-05 0:13 ` Tony Lindgren [this message]
2012-05-05 16:47 ` Russell King - ARM Linux
2012-05-05 17:16 ` Marc Zyngier
2012-05-05 17:20 ` Russell King - ARM Linux
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=20120505001323.GD5613@atomide.com \
--to=tony@atomide.com \
--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;
as well as URLs for NNTP newsgroup(s).