From: andy.tang@nxp.com
To: mturquette@baylibre.com, oss@buserror.net
Cc: sboyd@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
Yuantian Tang <andy.tang@nxp.com>
Subject: [PATCH 1/3] clk: qoriq: add t1023 soc support
Date: Wed, 19 Sep 2018 15:39:04 +0800 [thread overview]
Message-ID: <20180919073906.34187-1-andy.tang@nxp.com> (raw)
From: Yuantian Tang <andy.tang@nxp.com>
Add t1023 clock compatible string to the bindings.
Signed-off-by: Tang Yuantian <andy.tang@nxp.com>
---
.../devicetree/bindings/clock/qoriq-clock.txt | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/qoriq-clock.txt b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
index 97f46ad..34e1933 100644
--- a/Documentation/devicetree/bindings/clock/qoriq-clock.txt
+++ b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
@@ -37,6 +37,7 @@ Required properties:
* "fsl,ls1046a-clockgen"
* "fsl,ls1088a-clockgen"
* "fsl,ls2080a-clockgen"
+ * "fsl,t1023-clockgen"
Chassis-version clock strings include:
* "fsl,qoriq-clockgen-1.0": for chassis 1.0 clocks
* "fsl,qoriq-clockgen-2.0": for chassis 2.0 clocks
--
1.7.1
next reply other threads:[~2018-09-19 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 7:39 andy.tang [this message]
2018-09-19 7:39 ` [PATCH 2/3] powerpc: t102x: upgrade the legacy clock node andy.tang
2018-09-19 7:39 ` [PATCH 3/3] clk: qoriq: add t1023 soc support andy.tang
2018-10-20 23:53 ` [PATCH 2/3] powerpc: t102x: upgrade the legacy clock node Scott Wood
2018-10-22 1:34 ` Andy Tang
2018-10-22 5:20 ` Scott Wood
2018-10-22 7:48 ` Andy Tang
2018-10-16 6:17 ` [PATCH 1/3] clk: qoriq: add t1023 soc support Andy Tang
2018-10-17 15:27 ` Stephen Boyd
2018-10-18 1:00 ` Andy Tang
2018-10-19 6:28 ` Scott Wood
2018-10-19 6:47 ` Andy Tang
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=20180919073906.34187-1-andy.tang@nxp.com \
--to=andy.tang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=oss@buserror.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).