From: Adam Ford <aford173@gmail.com>
To: linux-clk@vger.kernel.org
Cc: abel.vesa@nxp.com, marex@denx.de, Adam Ford <aford173@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [RFC 1/3] dt-bindings: clock: imx8mn: Add media blk_ctl clock IDs
Date: Sat, 24 Oct 2020 11:20:13 -0500 [thread overview]
Message-ID: <20201024162016.1003041-2-aford173@gmail.com> (raw)
In-Reply-To: <20201024162016.1003041-1-aford173@gmail.com>
These will be used by the imx8mn for blk_ctl driver.
Signed-off-by: Adam Ford <aford173@gmail.com>
---
include/dt-bindings/clock/imx8mn-clock.h | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/include/dt-bindings/clock/imx8mn-clock.h b/include/dt-bindings/clock/imx8mn-clock.h
index 621ea0e87c67..2baaa2dccfd3 100644
--- a/include/dt-bindings/clock/imx8mn-clock.h
+++ b/include/dt-bindings/clock/imx8mn-clock.h
@@ -236,4 +236,15 @@
#define IMX8MN_CLK_END 215
+#define IMX8MN_CLK_MEDIA_BLK_CTL_MIPI_DSI_PCLK 0
+#define IMX8MN_CLK_MEDIA_BLK_CTL_MIPI_DSI_CLKREF 1
+#define IMX8MN_CLK_MEDIA_BLK_CTL_MIPI_CSI_PCLK 2
+#define IMX8MN_CLK_MEDIA_BLK_CTL_MIPI_CSI_ACLK 3
+#define IMX8MN_CLK_MEDIA_BLK_CTL_LCDIF_PIXEL 4
+#define IMX8MN_CLK_MEDIA_BLK_CTL_LCDIF_APB 5
+#define IMX8MN_CLK_MEDIA_BLK_CTL_ISI_PROC 6
+#define IMX8MN_CLK_MEDIA_BLK_CTL_ISI_APB 7
+#define IMX8MN_CLK_MEDIA_BLK_CTL_BUS_BLK 8
+#define IMX8MN_CLK_MEDIA_BLK_CTL_END 9
+
#endif
--
2.25.1
next prev parent reply other threads:[~2020-10-24 16:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 16:20 [RFC 0/3] clk: imx: Implement blk-ctl driver for i.MX8MN Adam Ford
2020-10-24 16:20 ` Adam Ford [this message]
2020-10-30 18:30 ` [RFC 1/3] dt-bindings: clock: imx8mn: Add media blk_ctl clock IDs Rob Herring
2020-10-24 16:20 ` [RFC 2/3] dt-bindings: reset: imx8mn: Add media blk_ctl reset IDs Adam Ford
2020-10-30 18:30 ` Rob Herring
2020-10-24 16:20 ` [RFC 3/3] clk: imx: Add blk-ctl driver for i.MX8MN Adam Ford
2021-01-27 14:56 ` Marek Vasut
2020-10-24 20:23 ` [RFC 0/3] clk: imx: Implement " Abel Vesa
2020-10-24 21:03 ` Adam Ford
2020-10-25 12:05 ` Abel Vesa
2020-10-25 12:18 ` Marek Vasut
2020-10-25 16:05 ` Adam Ford
2020-10-26 14:55 ` Abel Vesa
2020-10-26 15:12 ` Adam Ford
2020-10-26 15:44 ` Lucas Stach
2020-10-26 16:23 ` Adam Ford
2020-10-29 11:54 ` Lucas Stach
2020-10-29 12:18 ` Abel Vesa
2020-10-29 12:18 ` Adam Ford
2020-10-29 13:03 ` Lucas Stach
2020-10-27 9:38 ` Abel Vesa
2020-10-26 15:37 ` Lucas Stach
2020-10-27 9:31 ` Abel Vesa
2020-10-27 11:55 ` Abel Vesa
2020-10-28 1:28 ` Jacky Bai
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=20201024162016.1003041-2-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=abel.vesa@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--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).