From: Rob Herring <robh@kernel.org>
To: Jacky Bai <ping.bai@nxp.com>
Cc: "daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v2 1/2] Doc: bindings: Add binding doc for nxp system counter timer
Date: Tue, 18 Dec 2018 11:03:37 -0600 [thread overview]
Message-ID: <20181218170337.GA3394@bogus> (raw)
In-Reply-To: <1544592770-19996-1-git-send-email-ping.bai@nxp.com>
On Wed, Dec 12, 2018 at 05:28:23AM +0000, Jacky Bai wrote:
> Add the binding doc for nxp system counter timer module.
>
> Signed-off-by: Bai Ping <ping.bai@nxp.com>
> ---
> change v1->v2
> - remove the blank line at EOF
> ---
> .../devicetree/bindings/timer/nxp,sysctr_timer.txt | 26 ++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/timer/nxp,sysctr_timer.txt
>
> diff --git a/Documentation/devicetree/bindings/timer/nxp,sysctr_timer.txt b/Documentation/devicetree/bindings/timer/nxp,sysctr_timer.txt
> new file mode 100644
> index 0000000..21f1527
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/timer/nxp,sysctr_timer.txt
> @@ -0,0 +1,26 @@
> +NXP System Counter Module(sys_ctr)
> +
> +The system counter(sys_ctr) is a programmable system counter which provides
> +a shared time base to Cortex A15, A7, A53, A73, etc. it is intended for use in
> +applications where the counter is always powered and support multiple,
> +unrelated clocks.
> +
> +Required properties:
> +
> +- compatible : should be "nxp,sysctr-timer"
Only 1 version? Should be SoC specific.
> +- reg : Specifies the base physical address and size of the comapre
s/comapre/compare/
> + frame and the counter control, read & compare.
> +- interrupts : should be the compare frames' interrupt
> +- clock-frequency : Specifies the counter clock frequency.
> +
> +Example:
> +
> + system_counter: timer@306a0000 {
> + compatible = "nxp,sysctr-timer";
> + reg = <0x0 0x306a0000 0x0 0x10000>, /* system-counter-rd base */
> + <0x0 0x306b0000 0x0 0x10000>, /* system-counter-cmp base */
> + <0x0 0x306c0000 0x0 0x10000>; /* system-counter-ctrl base */
Are these really 64K in length? That wastes virtual space which can be
important on 32-bit systems.
> + clock-frequency = <8000000>;
> + interrupts = <GIC_SPI 47 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>;
> + };
> --
> 1.9.1
>
prev parent reply other threads:[~2018-12-18 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 5:28 [PATCH v2 1/2] Doc: bindings: Add binding doc for nxp system counter timer Jacky Bai
2018-12-12 5:28 ` [PATCH v2 2/2] driver: clocksource: Add nxp system counter timer driver support Jacky Bai
2018-12-12 18:48 ` Randy Dunlap
2019-01-08 9:33 ` Jacky Bai
2019-01-14 6:16 ` Jacky Bai
2019-01-14 15:45 ` Daniel Lezcano
2019-01-15 2:49 ` Jacky Bai
2018-12-18 17:03 ` Rob Herring [this message]
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=20181218170337.GA3394@bogus \
--to=robh@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ping.bai@nxp.com \
--cc=shawnguo@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).