[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1400600176-435-1-git-send-email-pdeschrijver@nvidia.com>
Date: Tue, 20 May 2014 18:36:08 +0300
From: Peter De Schrijver <pdeschrijver@...dia.com>
To: Peter De Schrijver <pdeschrijver@...dia.com>
CC: Russell King <linux@....linux.org.uk>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Stephen Warren <swarren@...dotorg.org>,
Thierry Reding <thierry.reding@...il.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>
Subject: [PATCH 0/3] Use Tegra's microsecond counter for udelay()
This patchset introduces support for Tegra's microsecond counter as the
udelay() timer. This is useful on Tegra SoCs which do not have an arch timer
such as Tegra20 and Tegra30. Using the microsecond counter instead of a delay
based loop avoids potential problems during cpu frequency changes.
The set consists of 3 patches:
Patch 1 introduces a new call which is used by the ARM architecture delay
timer code to prevent changing the delay timer after calibration is finished
and thus can be in use.
Patch 2 adds logic to choose the delay timer with the highest resolution. This
allows the same registration code to be used on all Tegra SoCs and yet use the
higher resolution arch timer when available (eg on Tegra114 or Tegra124).
Patch 3 adds the actual delay timer code.
Patch set has been verified on ventana (Tegra20), beaver (Tegra30),
dalmore (Tegra114) and jetson TK1 (Tegra124).
Peter De Schrijver (3):
kernel: add calibration_delay_done()
ARM: choose highest resolution delay timer
clocksource: tegra: Use uS counter as delay timer
arch/arm/lib/delay.c | 26 ++++++++++++++++++++++----
drivers/clocksource/tegra20_timer.c | 13 +++++++++++++
init/calibrate.c | 12 ++++++++++++
3 files changed, 47 insertions(+), 4 deletions(-)
--
1.7.7.rc0.72.g4b5ea.dirty
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists