From: Will Deacon <will@kernel.org>
To: Frank Li <Frank.li@nxp.com>, Xu Yang <xu.yang_2@nxp.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.Li@nxp.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Frank Li <frank.li@nxp.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
Joakim Zhang <qiangqing.zhang@nxp.com>,
Jacky Bai <ping.bai@nxp.com>
Subject: Re: [PATCH v3 0/6] perf/imx_ddr: Add i.MX8QM and pmu in DB (system interconnects)
Date: Mon, 24 Nov 2025 19:18:30 +0000 [thread overview]
Message-ID: <176399874665.521575.3051557105547982197.b4-ty@kernel.org> (raw)
In-Reply-To: <20251103-qm_dts-v3-0-2bfda8ee14c2@nxp.com>
On Mon, 03 Nov 2025 16:48:27 -0500, Frank Li wrote:
> dts: add soc specific compatible string for imx8qm, imx8qxp, imx8dxl in db.
> driver:
> - did some cleanup
> - add support for pmu in imx8dxl DB
> binding:
> - add compatible string for imx8qm, imx8qxp, imx8dxl in db
>
> [...]
Applied driver changes to will (for-next/perf), thanks!
[1/6] dt-bindings: perf: fsl-imx-ddr: Add compatible string for i.MX8QM, i.MX8QXP and i.MX8DXL
https://git.kernel.org/will/c/de8209e55408
[2/6] perf/imx_ddr: Move ida_alloc() from ddr_perf_init() to ddr_perf_probe()
https://git.kernel.org/will/c/66db99ffdfcb
[3/6] perf/imx_ddr: Get and enable optional clks
https://git.kernel.org/will/c/037e8cf67178
[4/6] perf/imx_ddr: Add support for PMU in DB (system interconnects)
https://git.kernel.org/will/c/11abb4e87b0e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-11-24 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 21:48 [PATCH v3 0/6] perf/imx_ddr: Add i.MX8QM and pmu in DB (system interconnects) Frank Li
2025-11-03 21:48 ` [PATCH v3 1/6] dt-bindings: perf: fsl-imx-ddr: Add compatible string for i.MX8QM, i.MX8QXP and i.MX8DXL Frank Li
2025-11-03 21:48 ` [PATCH v3 2/6] perf/imx_ddr: Move ida_alloc() from ddr_perf_init() to ddr_perf_probe() Frank Li
2025-11-03 21:48 ` [PATCH v3 3/6] perf/imx_ddr: Get and enable optional clks Frank Li
2025-11-03 21:48 ` [PATCH v3 4/6] perf/imx_ddr: Add support for PMU in DB (system interconnects) Frank Li
2025-11-03 21:48 ` [PATCH v3 5/6] arm64: dts: imx8qm: add ddr perf device node Frank Li
2025-12-29 2:50 ` Shawn Guo
2025-11-03 21:48 ` [PATCH v3 6/6] arm64: dts: imx8dxl-ss-ddr: Add DB (system interconnects) pmu support for i.MX8DXL Frank Li
2025-12-29 2:50 ` Shawn Guo
2025-11-24 19:18 ` Will Deacon [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=176399874665.521575.3051557105547982197.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Frank.li@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel-team@android.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ping.bai@nxp.com \
--cc=qiangqing.zhang@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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