From: josephl@nvidia.com (Joseph Lo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: tegra: enable arch_timer
Date: Thu, 4 Apr 2013 18:28:17 +0800 [thread overview]
Message-ID: <1365071297.1602.1.camel@jlo-ubuntu-64.nvidia.com> (raw)
In-Reply-To: <515CB1A6.6090308@wwwdotorg.org>
On Thu, 2013-04-04 at 06:48 +0800, Stephen Warren wrote:
> On 04/03/2013 03:34 PM, Rob Herring wrote:
> > On 04/03/2013 01:22 PM, Stephen Warren wrote:
> >> On 04/03/2013 07:28 AM, Rob Herring wrote:
> >>> On 04/03/2013 06:32 AM, Joseph Lo wrote:
> >> Rob, if I did apply this change, and you also apply that series of
> >> yours, what is the result: compile-time breakage, run-time breakage,
> >> just some redundant code that needs to be removed again?
> >
> > Compile-time breakage as the functions called here are being removed.
>
> OK, I definitely won't apply Joseph's patch then.
Agree. This patch is redundant, once Rob's patches go into mainline.
>
> Aside from that, I took the git branch you mentioned in the patch you
> linked to above, merged it into my dev tree, updated my bootloader to
> actually initialize the TSC correctly, and I see the following during
> boot, so I guess that's enough for:
>
> Tested-by: Stephen Warren <swarren@nvidia.com>
>
> on your patches.
>
> > [ 0.000000] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 4294967ms
> > [ 0.000000] Architected local timer running at 12.00MHz (virt).
> > [ 0.000000] Switching to timer-based delay loop
> > [ 117.431229] Calibrating delay loop (skipped), value calculated using timer frequency.. 24.00 BogoMIPS (lpj=120000)
> > [ 117.987221] Switching to clocksource arch_sys_counter
prev parent reply other threads:[~2013-04-04 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 11:32 [PATCH] clocksource: tegra: enable arch_timer Joseph Lo
2013-04-03 13:28 ` Rob Herring
2013-04-03 18:22 ` Stephen Warren
2013-04-03 21:34 ` Rob Herring
2013-04-03 22:48 ` Stephen Warren
2013-04-04 10:28 ` Joseph Lo [this message]
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=1365071297.1602.1.camel@jlo-ubuntu-64.nvidia.com \
--to=josephl@nvidia.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).