From: Yuantian Tang <andy.tang@nxp.com>
To: oss@buserror.net
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Yuantian Tang <andy.tang@nxp.com>
Subject: [PATCH 2/2 v3] clk: qoriq: add more compatibles strings
Date: Wed, 31 Oct 2018 14:57:36 +0800 [thread overview]
Message-ID: <20181031065736.32719-2-andy.tang@nxp.com> (raw)
In-Reply-To: <20181031065736.32719-1-andy.tang@nxp.com>
Add more SoC compatible strings to support more chips.
Signed-off-by: Yuantian Tang <andy.tang@nxp.com>
---
v3:
- undo deleting old bindings
- split the dts and driver to different patchset
.../devicetree/bindings/clock/qoriq-clock.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/qoriq-clock.txt b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
index 97f46ad..c655f28 100644
--- a/Documentation/devicetree/bindings/clock/qoriq-clock.txt
+++ b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
@@ -28,6 +28,12 @@ Required properties:
* "fsl,p4080-clockgen"
* "fsl,p5020-clockgen"
* "fsl,p5040-clockgen"
+ * "fsl,t1023-clockgen"
+ * "fsl,t1024-clockgen"
+ * "fsl,t1040-clockgen"
+ * "fsl,t1042-clockgen"
+ * "fsl,t2080-clockgen"
+ * "fsl,t2081-clockgen"
* "fsl,t4240-clockgen"
* "fsl,b4420-clockgen"
* "fsl,b4860-clockgen"
--
1.7.1
next prev parent reply other threads:[~2018-10-31 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 6:57 [PATCH 1/2 v3] powerpc/fsl: Use new clockgen binding Yuantian Tang
2018-10-31 6:57 ` Yuantian Tang [this message]
2018-11-05 20:27 ` [PATCH 2/2 v3] clk: qoriq: add more compatibles strings Rob Herring
2018-11-05 23:20 ` Stephen Boyd
2018-11-21 1:36 ` [PATCH 1/2 v3] powerpc/fsl: Use new clockgen binding Andy Tang
2018-11-26 1:19 ` Scott Wood
2018-12-12 1:57 ` Andy Tang
2018-12-22 4:35 ` Scott Wood
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=20181031065736.32719-2-andy.tang@nxp.com \
--to=andy.tang@nxp.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=mturquette@baylibre.com \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--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).