From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
sboyd@kernel.org, mturquette@baylibre.com, shawnguo@kernel.org,
s.hauer@pengutronix.de
Cc: aisheng.dong@nxp.com, l.stach@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V3 0/7] imx: support i.MX93 SRC and mediamix blk ctrl
Date: Mon, 6 Jun 2022 09:50:18 +0800 [thread overview]
Message-ID: <20220606015025.180840-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
V3:
Move src yaml to power directory.
Update slice name to slices
V2:
yaml fix
This patchset is to support i.MX93 SRC and mediamix blk ctrl.
SRC functions as power domain provider as i.MX8M GPC.
mediamix blk ctrl is similar with i.MX8M blk ctrl, but much simplier from
software view.
Export of_clk_bulk_get_all for driver usage.
Add bindings and dts node
Based on:
https://patchwork.kernel.org/project/linux-arm-kernel/cover/20220510124050.398891-1-peng.fan@oss.nxp.com/
Peng Fan (7):
dt-bindings: soc: add i.MX93 SRC
dt-bindings: soc: add i.MX93 mediamix blk ctrl
clk: export of_clk_bulk_get_all
soc: imx: add i.MX93 SRC power domain driver
soc: imx: add i.MX93 media blk ctrl driver
arm64: dts: imx93: add src node
arm64: dts: imx93: add mediamix blk ctrl node
.../bindings/power/fsl,imx93-src.yaml | 96 +++++
.../soc/imx/fsl,imx93-media-blk-ctrl.yaml | 80 +++++
arch/arm64/boot/dts/freescale/imx93.dtsi | 38 ++
drivers/clk/clk-bulk.c | 3 +-
drivers/soc/imx/Kconfig | 10 +
drivers/soc/imx/Makefile | 1 +
drivers/soc/imx/imx93-blk-ctrl.c | 333 ++++++++++++++++++
drivers/soc/imx/imx93-pd.c | 271 ++++++++++++++
include/dt-bindings/power/fsl,imx93-power.h | 17 +
include/linux/clk.h | 2 +
10 files changed, 850 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/power/fsl,imx93-src.yaml
create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml
create mode 100644 drivers/soc/imx/imx93-blk-ctrl.c
create mode 100644 drivers/soc/imx/imx93-pd.c
create mode 100644 include/dt-bindings/power/fsl,imx93-power.h
--
2.25.1
next reply other threads:[~2022-06-06 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 1:50 Peng Fan (OSS) [this message]
2022-06-06 1:50 ` [PATCH V3 1/7] dt-bindings: soc: add i.MX93 SRC Peng Fan (OSS)
2022-06-06 1:50 ` [PATCH V3 2/7] dt-bindings: soc: add i.MX93 mediamix blk ctrl Peng Fan (OSS)
2022-06-06 1:50 ` [PATCH V3 3/7] clk: export of_clk_bulk_get_all Peng Fan (OSS)
2022-06-06 1:50 ` [PATCH V3 4/7] soc: imx: add i.MX93 SRC power domain driver Peng Fan (OSS)
2022-06-06 1:50 ` [PATCH V3 5/7] soc: imx: add i.MX93 media blk ctrl driver Peng Fan (OSS)
2022-06-06 1:50 ` [PATCH V3 6/7] arm64: dts: imx93: add src node Peng Fan (OSS)
2022-06-06 1:50 ` [PATCH V3 7/7] arm64: dts: imx93: add mediamix blk ctrl node Peng Fan (OSS)
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=20220606015025.180840-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).