From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: re-adding clocksource_get_next ?
Date: Mon, 12 Apr 2010 08:02:24 +0200 [thread overview]
Message-ID: <4BC2B770.3020501@st.com> (raw)
In-Reply-To: <x2p1f1b08da1004091358z1d185aacya6c0fa2f55322fc7@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello John,
john stultz wrote:
> On Thu, Apr 8, 2010 at 11:53 PM, Giuseppe CAVALLARO
> <peppe.cavallaro@st.com> wrote:
>> Hello!
>> this function was removed in the past but I've not clear all the details.
>> While testing LLTng, I wrote the patch, in attachment, that re-adds it
>> again.
>> The clocksource_get_next returns the first clock source available
>> (without looking at the rating).
>> In my environment, a clock source is a TMU channel (e.g. TMU1) and,
>> indeed, clocksource_get_next works fine.
>
> Could you provide some more details as to why you need raw access to
> the clocksource, instead of using something like ktime_get(),
> getrawmonotonic() or sched_clock()?
I wanted to directly read the value of the TCNT register of a TMU
channel registered as clocksource in an SH platform.
My idea was to get the first clocksource available and than use the read
hook to get its raw value.
Indeed, on SH4, the clocksource_get_next returns the TMU channel 1
(usually registered as clocksource); the clk->reads points to
sh_tmu_clocksource_read (drivers/clocksource/sh_tmu.c). This returns the
value of the timer count register (TCNT).
Best Regards,
Giuseppe
> thanks
> -john
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJLwrdqAAoJEAm9vY9Tshdv2HAH/RdL0cKvYAjcnS4lzJGppbzX
NdZL6WTW3wNfrqBzm7g8OGy+ZX3Fd+yQKbR41qGcH1agQ5JKMN5aDLzVhw91CG9o
aJAqsYyMVxetDa1iDxmqHpwctbeQfACwxztX1wceG/YuAGM7XXHevVN/ywQZn10c
qxSb+bgNr4T489f7EkCLTwvk+iutRY0TRQIJX0/40qIO/UGpjiNODkfbCXAaU2QC
Cw5zq59UY7gvbnrAmjthxTq91kWqUAunk4UaliSaxV7n+JJziWPKDQ7iXzbSk/sv
CJmec+/1ZmnISBYyjCMtRX5o0xDjxfWgWSVI7YiS7lPOtV+b/QN4a5gr/g1UP7w=
=wuHC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-12 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 6:53 re-adding clocksource_get_next ? Giuseppe CAVALLARO
2010-04-09 20:58 ` john stultz
2010-04-12 6:02 ` Giuseppe CAVALLARO [this message]
2010-04-12 18:50 ` john stultz
2010-04-13 5:44 ` Giuseppe CAVALLARO
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=4BC2B770.3020501@st.com \
--to=peppe.cavallaro@st.com \
--cc=johnstul@us.ibm.com \
--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