linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Muni Sekhar <munisekharrms@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, LKML <linux-kernel@vger.kernel.org>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Time: new clocksource
Date: Tue, 7 Dec 2021 13:03:07 +0530	[thread overview]
Message-ID: <CAHhAz+iZe4A9bi9tvwqpHaV1ari76r2bXcO1E6Bm88Cc7XFq+A@mail.gmail.com> (raw)
In-Reply-To: <fe9dbf81-e060-36ab-b769-215af3d65ba7@linaro.org>

On Sat, Dec 4, 2021 at 3:18 AM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> 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
/var/log/kern.log file use a absolute time, like "Nov 29 12:26:13", as
well as relative time in seconds and microseconds since startup , like
"[1263900.984287]

Is the relative time calculated by the clocksource driver module (tsc
or acpi_pm)?

Which module is responsible for resulting in the absolute time? Is
absolute time synchronized across multiple systems connected on the
network?
>
>
> --
> <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



-- 
Thanks,
Sekhar

  parent reply	other threads:[~2021-12-07  7:33 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
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 [this message]
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=CAHhAz+iZe4A9bi9tvwqpHaV1ari76r2bXcO1E6Bm88Cc7XFq+A@mail.gmail.com \
    --to=munisekharrms@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).