From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: tglx@linutronix.de, LKML <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Time: new clocksource
Date: Mon, 6 Dec 2021 07:29:32 +0100 [thread overview]
Message-ID: <a5192a80-0401-78fd-6fb3-e58a3b5a3923@linaro.org> (raw)
In-Reply-To: <CAHhAz+iEQTtfxXB8sNEL4WxFjUZo5LYTo4EVyH0mT2=NH3VaUA@mail.gmail.com>
On 06/12/2021 07:00, Muni Sekhar wrote:
> 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
> I don't see the option in menuconfig to build the clocksource driver
> as a loadable kernel module, for example CONFIG_X86_PM_TIMER=m instead
> of CONFIG_X86_PM_TIMER=y.
> So a clocksource driver should always be part of the kernel built-in
> module?
Yes, that is the case today.
> If so, what's the reason for that?
The timer is a component needed at boot time, so a module version does
really not make sense.
So I would return back the question : what is the reason for a module?
>> 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
>
>
>
--
<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-06 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:50 Muni Sekhar
2021-12-03 21:48 ` Daniel Lezcano
2021-12-06 6:00 ` Muni Sekhar
2021-12-06 6:29 ` Daniel Lezcano [this message]
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=a5192a80-0401-78fd-6fb3-e58a3b5a3923@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
all inboxes | Powered by JetHome®