From: Kirill Tkhai <tkhai@yandex.ru>
To: sparclinux@vger.kernel.org
Subject: Clock event support on SPARC32
Date: Mon, 05 Dec 2011 21:33:17 +0000 [thread overview]
Message-ID: <1323120797.3274.20.camel@hp> (raw)
Hello!
I'm not sending a patch, just asking a question.
There is no clock event support on SPARC32, but it's possible to
implement it.
The plan is to use local timers as periodic and one-shot clock events,
while global timer is a continuous clock source. It ticks and increases
internal counter of tick number every 2 seconds (it's possible to use
more, but I use a round number). The number "counter * size_of_tick +
master_l10_counter" gives us the continuous clocksource.
The only problem is a fact that LEON doesn't have a master_l10_counter,
but it's possible to use HZ-lenght clocksource for this case.
If we get clocksource support, we'll get HIGH_RES_TIMERS.
So, the question is "will this feature be useful for SPARC?". I did the
same on 2.6.33 for my work, I can do this for version 3.*.
Regards,
Kirill Tkhai
next reply other threads:[~2011-12-05 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 21:33 Kirill Tkhai [this message]
2011-12-29 12:42 ` Clock event support on SPARC32 Sam Ravnborg
2012-01-28 22:32 ` Kirill Tkhai
2012-02-05 14:39 ` Sam Ravnborg
2012-02-06 21:55 ` Kirill Tkhai
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=1323120797.3274.20.camel@hp \
--to=tkhai@yandex.ru \
--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.