From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Muni Sekhar <munisekharrms@gmail.com>,
tglx@linutronix.de, LKML <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Time: new clocksource
Date: Fri, 3 Dec 2021 22:48:08 +0100 [thread overview]
Message-ID: <fe9dbf81-e060-36ab-b769-215af3d65ba7@linaro.org> (raw)
In-Reply-To: <CAHhAz+jpmksehY4BSH9jJPYuY+jykSHtx9TNiG-gAkq10zaXSQ@mail.gmail.com>
Hi Sekhar,
On 03/12/2021 17:50, Muni Sekhar wrote:
> Hi All,
>
> We have a Digital PLL with 64 bit timer counter hardware and the
> counter is accessible from the CPU over the PCIe bus.
>
> Is it possible to add this timer counter hardware as new clocksource
> driver? To do this, can someone please point me to the existing
> reference source code(or patch) for this task.
You can refer to the drivers located in drivers/clocksource
git annotate on one of the driver can give you the initial commit where
recent submissions explain the timer internals.
> Suppose if it is possible to add a new clocksource driver for this
> hardware then does any userspace get_timestamp* API would get the time
> from this new hardware?
It should if the timer is selected as the clocksource
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2021-12-03 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:50 Time: new clocksource Muni Sekhar
2021-12-03 21:48 ` Daniel Lezcano [this message]
2021-12-06 6:00 ` Muni Sekhar
2021-12-06 6:29 ` Daniel Lezcano
2021-12-06 7:00 ` Muni Sekhar
2021-12-07 7:33 ` Muni Sekhar
2021-12-08 9:10 ` Valdis Klētnieks
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=fe9dbf81-e060-36ab-b769-215af3d65ba7@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=munisekharrms@gmail.com \
--cc=tglx@linutronix.de \
/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).