From: Aisheng Dong <aisheng.dong@nxp.com>
To: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>
Subject: [PATCH RESEND v1 4/4] dt-bindings: imx8-clock: add a53 and a72 clock id
Date: Fri, 11 Jan 2019 11:56:09 +0000 [thread overview]
Message-ID: <1547207400-28307-5-git-send-email-aisheng.dong@nxp.com> (raw)
In-Reply-To: <1547207400-28307-1-git-send-email-aisheng.dong@nxp.com>
Add a53 and a72 clock id, as there's still no users, we update
IMX_LSIO_MEM_CLK base to start from 6 to allow a53 and a72 clock
id to be continued with a35 clk.
Cc: Stephen Boyd <sboyd@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>
Cc: Sascha Hauer <kernel@pengutronix.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>
Cc: Michael Turquette <mturquette@baylibre.com>
Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
---
include/dt-bindings/clock/imx8-clock.h | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/dt-bindings/clock/imx8-clock.h b/include/dt-bindings/clock/imx8-clock.h
index 4236818..2f1aa2f 100644
--- a/include/dt-bindings/clock/imx8-clock.h
+++ b/include/dt-bindings/clock/imx8-clock.h
@@ -13,10 +13,12 @@
/* CPU */
#define IMX_A35_CLK 1
+#define IMX_A53_CLK 2
+#define IMX_A72_CLK 3
/* LSIO SS */
-#define IMX_LSIO_MEM_CLK 2
-#define IMX_LSIO_BUS_CLK 3
+#define IMX_LSIO_MEM_CLK 6
+#define IMX_LSIO_BUS_CLK 7
#define IMX_LSIO_PWM0_CLK 10
#define IMX_LSIO_PWM1_CLK 11
#define IMX_LSIO_PWM2_CLK 12
--
2.7.4
next prev parent reply other threads:[~2019-01-11 11:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 11:55 [PATCH RESEND v1 0/4] dt-binding: clk: prepare for imx8qm clock support Aisheng Dong
2019-01-11 11:55 ` [PATCH RESEND v1 1/4] dt-bindings: fsl: scu: add fallback compatible string for clock Aisheng Dong
2019-01-21 23:25 ` Rob Herring
2019-01-22 19:05 ` Stephen Boyd
2019-01-11 11:56 ` [PATCH RESEND v1 2/4] dt-bindings: fsl: scu: add imx8qm scu clock support Aisheng Dong
2019-01-21 23:27 ` Rob Herring
2019-01-22 12:58 ` Aisheng Dong
2019-01-22 19:06 ` Stephen Boyd
2019-01-11 11:56 ` [PATCH RESEND v1 3/4] clk: imx: scu: add fallback compatible string support Aisheng Dong
2019-01-11 11:56 ` Aisheng Dong [this message]
2019-01-22 0:10 ` [PATCH RESEND v1 4/4] dt-bindings: imx8-clock: add a53 and a72 clock id Rob Herring
2019-01-22 12:59 ` Aisheng Dong
2019-01-30 16:45 ` Rob Herring
2019-01-16 5:40 ` [PATCH RESEND v1 0/4] dt-binding: clk: prepare for imx8qm clock support Aisheng Dong
2019-01-16 11:02 ` Shawn Guo
2019-01-22 19:06 ` Stephen Boyd
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=1547207400-28307-5-git-send-email-aisheng.dong@nxp.com \
--to=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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).