From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] kernel: add calibration_delay_done()
Date: Tue, 20 May 2014 21:41:31 +0400 [thread overview]
Message-ID: <537B93CB.3040109@cogentembedded.com> (raw)
In-Reply-To: <1400600176-435-2-git-send-email-pdeschrijver@nvidia.com>
On 05/20/2014 07:36 PM, Peter De Schrijver wrote:
> Add calibration_delay_done() call and dummy implementation. This allows
> architectures to stop accepting registrations for new timer based delay
> functions.
> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> ---
> init/calibrate.c | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
> diff --git a/init/calibrate.c b/init/calibrate.c
> index 520702d..31cae76 100644
> --- a/init/calibrate.c
> +++ b/init/calibrate.c
> @@ -262,6 +262,16 @@ unsigned long __attribute__((weak)) calibrate_delay_is_known(void)
> return 0;
> }
>
> +/*
> + * Indicate the cpu delay calibration is done. This can be used by
> + * architectures to stop accepting delay timer registrations after this point.
> + */
> +
> +void __attribute__((weak)) calibration_delay_done(void)
> +{
> + return;
Not really needed.
> +}
> +
> void calibrate_delay(void)
> {
> unsigned long lpj;
WBR, Sergei
next prev parent reply other threads:[~2014-05-20 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 15:36 [PATCH 0/3] Use Tegra's microsecond counter for udelay() Peter De Schrijver
2014-05-20 15:36 ` [PATCH 1/3] kernel: add calibration_delay_done() Peter De Schrijver
2014-05-20 17:41 ` Sergei Shtylyov [this message]
2014-05-20 15:36 ` [PATCH 2/3] ARM: choose highest resolution delay timer Peter De Schrijver
2014-05-20 15:36 ` [PATCH 3/3] clocksource: tegra: Use uS counter as " Peter De Schrijver
2014-05-20 18:37 ` Stephen Warren
2014-05-22 13:56 ` Thierry Reding
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=537B93CB.3040109@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).