From: Nickhu <nickhu@andestech.com>
To: <greentime@andestech.com>, <linux-kernel@vger.kernel.org>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<deanbo422@gmail.com>, <peterz@infradead.org>, <mingo@redhat.com>,
<acme@kernel.org>, <alexander.shishkin@linux.intel.com>,
<jolsa@redhat.com>, <namhyung@kernel.org>, <arnd@arndb.de>,
<sboyd@codeaurora.org>, <geert@linux-m68k.org>,
<zong@andestech.com>, <ebiederm@xmission.com>,
<akpm@linux-foundation.org>, <gregkh@linuxfoundation.org>,
<pombredanne@nexb.com>, <tglx@linutronix.de>,
<kstewart@linuxfoundation.org>, <devicetree@vger.kernel.org>
Cc: Nickhu <nickhu@andestech.com>, <green.hu@gmail.com>
Subject: [PATCH 5/5] nds32: Add document for NDS32 PMU.
Date: Thu, 18 Oct 2018 16:43:17 +0800 [thread overview]
Message-ID: <c0a80d2db642b1d9547ff412d91baa9927b68aac.1539745993.git.nickhu@andestech.com> (raw)
In-Reply-To: <cover.1539745993.git.nickhu@andestech.com>
The document for how to add NDS32 PMU
in devicetree.
Signed-off-by: Nickhu <nickhu@andestech.com>
---
Documentation/devicetree/bindings/nds32/pmu.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nds32/pmu.txt
diff --git a/Documentation/devicetree/bindings/nds32/pmu.txt b/Documentation/devicetree/bindings/nds32/pmu.txt
new file mode 100644
index 000000000000..02762b850e59
--- /dev/null
+++ b/Documentation/devicetree/bindings/nds32/pmu.txt
@@ -0,0 +1,17 @@
+* NDS32 Performance Monitor Units
+
+NDS32 core have a PMU for counting cpu and cache events like cache misses.
+The NDS32 PMU representation in the device tree should be done as under:
+
+Required properties:
+
+- compatilbe :
+ "andestech,atcpmu"
+
+- interrupts : The interrupt number for NDS32 PMU is 13.
+
+Example:
+pmu{
+ compatible = "andestech,atcpmu";
+ interrupts = <13>;
+}
--
2.17.0
next prev parent reply other threads:[~2018-10-18 8:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 8:43 [PATCH 0/5] nds32: Perf support Nickhu
2018-10-18 8:43 ` [PATCH 1/5] nds32: Perf porting Nickhu
2018-10-18 14:23 ` Mark Rutland
2018-10-22 10:18 ` Nick Hu
2018-10-22 13:15 ` Mark Rutland
2018-10-18 8:43 ` [PATCH 2/5] nds32: Fix bug in bitfield.h Nickhu
2018-10-18 14:26 ` Mark Rutland
2018-10-22 10:19 ` Nick Hu
2018-10-18 8:43 ` [PATCH 3/5] nds32: Add perf call-graph support Nickhu
2018-10-18 8:43 ` [PATCH 4/5] nds32: Fix perf multiple events map to same counter Nickhu
2018-10-18 14:29 ` Mark Rutland
2018-10-22 10:20 ` Nick Hu
2018-10-18 8:43 ` Nickhu [this message]
2018-10-18 14:31 ` [PATCH 5/5] nds32: Add document for NDS32 PMU Mark Rutland
2018-10-22 10:23 ` Nick Hu
2018-10-22 13:17 ` Mark Rutland
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=c0a80d2db642b1d9547ff412d91baa9927b68aac.1539745993.git.nickhu@andestech.com \
--to=nickhu@andestech.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnd@arndb.de \
--cc=deanbo422@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=green.hu@gmail.com \
--cc=greentime@andestech.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=zong@andestech.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).