From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Ajay Kumar <ajaykumar.rs@samsung.com>
Cc: mark.rutland@arm.com, shaik.ameer@samsung.com,
robin.murphy@arm.com, nleeder@codeaurora.org,
shameerali.kolothum.thodi@huawei.com, robh+dt@kernel.org,
alim.akhtar@samsung.com, will@kernel.org, joro@8bytes.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] Documentation: perf: Add documentation for arm-smmu-v3-pmcg
Date: Mon, 13 Jul 2020 09:41:18 +0100 [thread overview]
Message-ID: <20200713094118.00004aea@Huawei.com> (raw)
In-Reply-To: <20200712163341.61410-3-ajaykumar.rs@samsung.com>
On Sun, 12 Jul 2020 22:03:39 +0530
Ajay Kumar <ajaykumar.rs@samsung.com> wrote:
> This patch adds devicetree binding for perf/arm_smmuv3_pmu driver.
>
> Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
New bindings want to be in yaml format.
> ---
> .../bindings/perf/arm-smmu-v3-pmcg.txt | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/perf/arm-smmu-v3-pmcg.txt
>
> diff --git a/Documentation/devicetree/bindings/perf/arm-smmu-v3-pmcg.txt b/Documentation/devicetree/bindings/perf/arm-smmu-v3-pmcg.txt
> new file mode 100644
> index 000000000000..a20fe68ce149
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/perf/arm-smmu-v3-pmcg.txt
> @@ -0,0 +1,21 @@
> +* ARM SMMU V3 PMCG
> +
> +Required properties:
> +
> +- compatible: should be "arm-smmu-v3-pmu"
> +
> +- reg: (standard registers property) physical address and size
> + of the performance counters registers block.
> + If Page 1 is present, specify the same.
> +
> +- interrupts: (standard interrupt property) single interrupt
> + generated by the SMMU PMU control block
> +
> +Example:
> +
> + pmcg@20002000 {
> + compatible = "arm-smmu-v3-pmu";
> + reg = <0x0 0x20002000 0x0 0x1000>,
> + <0x0 0x20022000 0x0 0xE00>; /* Page 1 */
> + interrupts = <0 181 4>;
> + };
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-13 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200712165509epcas5p29e66777a4e0115420b9104ba5aa83f57@epcas5p2.samsung.com>
2020-07-12 16:33 ` [PATCH 0/4] Add DT support for arm_smmuv3_pmu driver Ajay Kumar
2020-07-12 16:33 ` [PATCH 1/4] perf/smmuv3: Remove dependency on CONFIG_ACPI Ajay Kumar
2020-07-12 16:33 ` [PATCH 2/4] Documentation: perf: Add documentation for arm-smmu-v3-pmcg Ajay Kumar
2020-07-13 8:41 ` Jonathan Cameron [this message]
2020-07-12 16:33 ` [PATCH 3/4] perf/smmuv3: add device tree support Ajay Kumar
2020-07-12 16:33 ` [PATCH 4/4] perf/smmuv3: fix crash when platdata not specified Ajay Kumar
2020-07-13 8:46 ` Jonathan Cameron
2020-07-13 9:46 ` Robin Murphy
2020-07-13 9:42 ` [PATCH 0/4] Add DT support for arm_smmuv3_pmu driver Robin Murphy
2020-07-13 9:57 ` John Garry
2020-07-13 10:17 ` Ajay kumar
2020-07-13 10:28 ` Robin Murphy
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=20200713094118.00004aea@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=ajaykumar.rs@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nleeder@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=shaik.ameer@samsung.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.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).