From: Alexey Klimov <klimov.linux@gmail.com>
To: linux-samsung-soc@vger.kernel.org, daniel.lezcano@linaro.org,
dianders@chromium.org, chirantan@chromium.org
Cc: klimov.linux@gmail.com, t.dakhran@gmail.com,
k.kozlowski@samsung.com, kgene@kernel.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org, yury.norov@gmail.com
Subject: [RFC PATCH 2/3] documentation: dt: mct: add desc of optional property use-cp15-phys-counter
Date: Tue, 28 Jul 2015 00:28:44 +0300 [thread overview]
Message-ID: <1438032524.17734.48.camel@gmail.com> (raw)
Signed-off-by: Alexey Klimov <klimov.linux@gmail.com>
---
.../devicetree/bindings/timer/samsung,exynos4210-mct.txt | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.txt b/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.txt
index 167d5da..c7f6354 100644
--- a/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.txt
+++ b/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.txt
@@ -36,6 +36,16 @@ Required properties:
interrupt might be specified, meaning that all local timers use the same
per processor interrupt.
+Optional properties:
+
+- use-cp15-phys-counter : set to advise mct clocksource driver to use ARM
+ arch timer 64-bit counter as main counter. Access to this coprocessor
+ counter is faster than access to same counter in mct mmio region.
+ It was discovered that mct and ARM arch timer are same underlying hardware
+ on some SoCs.
+ Only supported for Exynos5-based 32-bit systems which follow the ARMv7
+ architecture.
+
Example 1: In this example, the IP contains two local timers, using separate
interrupts, so two local timer interrupts have been specified,
in addition to four global timer interrupts.
--
2.1.4
reply other threads:[~2015-07-27 21:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1438032524.17734.48.camel@gmail.com \
--to=klimov.linux@gmail.com \
--cc=chirantan@chromium.org \
--cc=daniel.lezcano@linaro.org \
--cc=dianders@chromium.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=t.dakhran@gmail.com \
--cc=tglx@linutronix.de \
--cc=yury.norov@gmail.com \
/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).