From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc - generic clock event support
Date: Thu, 05 Apr 2012 14:23:08 +0000 [thread overview]
Message-ID: <4F7DAACC.1040207@gaisler.com> (raw)
In-Reply-To: <20120404200704.GA16958@merkur.ravnborg.org>
Sam Ravnborg wrote:
> On Thu, Apr 05, 2012 at 08:55:21AM +0200, Konrad Eisele wrote:
>> Sam Ravnborg wrote:
>>> I have now finised revising the patch to
>>> provide support for generic clock event support
>>> on sparc32.
>>>
>>> The main focus has been to extend the core functionality
>>> (within sparc32) to allow us to share a lot of code between
>>> leon and the other platfroms.
>>>
>>> I have in this process updated a few bits here and there.
>>> The patch set is build tested for leon, and
>>> runtime tested on my ss5 (sun4m).
>>
>> I'll test it today on Leon.
>
> Thanks Konrad!
> I hope I did not broke it beyond repair :-)
>
> Sam
>
>
I runtime tested your patch. For single-CPU the patch works
fine. For SMP I cannot test because Leon-SMP for 3.x doesnt
work right now, also without your patch. The last version
that I could verify LEON-SMP was 2.6.36, 3.0 should also work,
however there your patches dont apply. I'll have to make
Leon-SMP work with 3.4 first , then I can test the SMP part
of the patch. However I'll write this on my todo list for
after easter. As for Leon-SMP is broken right now I would
vote for that your patches are applied now and after that to
try to fix Leon-SMP.
-- Konrad
------ single cpu -------------
# cd /proc
# cat cpuinfo
cpu : LEON
fpu : GRFPU-Lite
promlib : Version 0 Revision 0
prom : 0.0
type : leon
ncpus probed : 1
ncpus active : 1
CPU0Bogo : 201.11
CPU0ClkTck : 202000
MMU type : LEON
contexts : 256
nocache total : 3145728
nocache used : 114432
# cat timer_list
Timer List Version: v0.6
HRTIMER_MAX_CLOCK_BASES: 3
now at 21370769625 nsecs
cpu: 0
clock 0:
.base: f03c1750
.index: 0
.resolution: 10000000 nsecs
.get_time: ktime_get
active timers:
clock 1:
.base: f03c1788
.index: 1
.resolution: 10000000 nsecs
.get_time: ktime_get_real
active timers:
clock 2:
.base: f03c17c0
.index: 2
.resolution: 10000000 nsecs
.get_time: ktime_get_boottime
active timers:
Tick Device: mode: 0
Per CPU device: 0
Clock Event Device: timer_ce
max_delta_ns: 0
min_delta_ns: 0
mult: 4294967
shift: 32
mode: 2
next_event: 2147483646999999999 nsecs
set_next_event: <00000000>
set_mode: timer_ce_set_mode
event_handler: tick_handle_periodic
retries: 0
#
next prev parent reply other threads:[~2012-04-05 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 20:07 sparc - generic clock event support Sam Ravnborg
2012-04-05 6:55 ` Konrad Eisele
2012-04-05 7:26 ` Sam Ravnborg
2012-04-05 14:23 ` Konrad Eisele [this message]
2012-04-05 15:12 ` Sam Ravnborg
2012-04-20 8:21 ` Konrad Eisele
2012-04-20 14:46 ` Sam Ravnborg
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=4F7DAACC.1040207@gaisler.com \
--to=konrad@gaisler.com \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.