From: Shawn Guo <shawnguo@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: will@kernel.org, mark.rutland@arm.com, frank.li@nxp.com,
festevam@gmail.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-imx@nxp.com
Subject: Re: [PATCH v2 3/3] arm64: dts: imx93: add ddr performance monitor node
Date: Sun, 14 May 2023 11:08:02 +0800 [thread overview]
Message-ID: <20230514030802.GL727834@dragon> (raw)
In-Reply-To: <20230418102910.2065651-3-xu.yang_2@nxp.com>
On Tue, Apr 18, 2023 at 06:29:10PM +0800, Xu Yang wrote:
> Add performance monitor.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
Please send DTS changes in a separate series after drivers/bindings
changes are accepted.
Shawn
>
> ---
> Changes from v2:
> - no change
>
> diff --git a/arch/arm64/boot/dts/freescale/imx93.dtsi b/arch/arm64/boot/dts/freescale/imx93.dtsi
> index 2076f9c9983a..be8a581c7454 100644
> --- a/arch/arm64/boot/dts/freescale/imx93.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx93.dtsi
> @@ -725,5 +725,11 @@ media_blk_ctrl: system-controller@4ac10000 {
> #power-domain-cells = <1>;
> status = "disabled";
> };
> +
> + ddr-pmu@4e300dc0 {
> + compatible = "fsl,imx93-ddr-pmu";
> + reg = <0x4e300dc0 0x200>;
> + interrupts = <GIC_SPI 90 IRQ_TYPE_LEVEL_HIGH>;
> + };
> };
> };
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-05-14 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 10:29 [PATCH v2 1/3] drivers/perf: imx_ddr: Add support for NXP i.MX9 SoC DDRC PMU driver Xu Yang
2023-04-18 10:29 ` [PATCH v2 2/3] dt-bindings: perf: fsl-imx-ddr: Add i.MX93 compatible Xu Yang
2023-04-18 10:29 ` [PATCH v2 3/3] arm64: dts: imx93: add ddr performance monitor node Xu Yang
2023-05-14 3:08 ` Shawn Guo [this message]
2023-06-09 14:06 ` Shawn Guo
2023-05-04 3:25 ` [PATCH v2 1/3] drivers/perf: imx_ddr: Add support for NXP i.MX9 SoC DDRC PMU driver Xu Yang
2023-05-29 7:02 ` Xu Yang
2023-06-08 9:18 ` Mark Rutland
2023-06-09 11:16 ` Will Deacon
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=20230514030802.GL727834@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will@kernel.org \
--cc=xu.yang_2@nxp.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).