From: Wei Fang <wei.fang@nxp.com>
To: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
festevam@gmail.com, abelvesa@kernel.org, peng.fan@nxp.com
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] add NETCMIX block control support on i.MX95
Date: Tue, 9 Jul 2024 15:36:01 +0800 [thread overview]
Message-ID: <20240709073603.1967609-1-wei.fang@nxp.com> (raw)
The NETCMIX block control consists of registers for configuration of
peripherals in the NETC domain, such as MQS, SAI and NETC. So add the
NETCMIX block control support on i.MX95 platform.
Wei Fang (3):
dt-bindings: clock: add i.MX95 NETCMIX block control
clk: imx95: enable the clock of NETCMIX block control
arm64: dts: imx95: Add NETCMIX block control support
.../devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml | 1 +
arch/arm64/boot/dts/freescale/imx95.dtsi | 12 ++++++++++++
drivers/clk/imx/clk-imx95-blk-ctl.c | 1 +
3 files changed, 14 insertions(+)
--
2.34.1
next reply other threads:[~2024-07-09 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 7:36 Wei Fang [this message]
2024-07-09 7:36 ` [PATCH 1/3] dt-bindings: clock: add i.MX95 NETCMIX block control Wei Fang
2024-07-09 16:36 ` Rob Herring (Arm)
2024-07-09 7:36 ` [PATCH 2/3] clk: imx95: enable the clock of " Wei Fang
2024-07-09 14:13 ` Peng Fan
2024-07-10 2:09 ` Wei Fang
2024-07-10 2:22 ` Peng Fan
2024-07-10 2:34 ` Wei Fang
2024-07-09 7:36 ` [PATCH 3/3] arm64: dts: imx95: Add NETCMIX block control support Wei Fang
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=20240709073603.1967609-1-wei.fang@nxp.com \
--to=wei.fang@nxp.com \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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