devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: linuxppc-dev@lists.ozlabs.org
Cc: Yangbo Lu <yangbo.lu@nxp.com>,
	linux-mmc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Scott Wood <oss@buserror.net>
Subject: [PATCH v11 1/5] dt: bindings: update Freescale DCFG compatible
Date: Sat, 16 Jul 2016 21:50:18 -0500	[thread overview]
Message-ID: <1468723822-30457-2-git-send-email-oss@buserror.net> (raw)
In-Reply-To: <1468723822-30457-1-git-send-email-oss@buserror.net>

From: yangbo lu <yangbo.lu@nxp.com>

Update Freescale DCFG compatible with 'fsl,<chip>-dcfg' instead
of 'fsl,ls1021a-dcfg' to include more chips such as ls1021a,
ls1043a, and ls2080a.

Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Scott Wood <oss@buserror.net>
---
 Documentation/devicetree/bindings/arm/fsl.txt | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/arm/fsl.txt b/Documentation/devicetree/bindings/arm/fsl.txt
index dbbc095..713c1ae 100644
--- a/Documentation/devicetree/bindings/arm/fsl.txt
+++ b/Documentation/devicetree/bindings/arm/fsl.txt
@@ -119,7 +119,11 @@ Freescale DCFG
 configuration and status for the device. Such as setting the secondary
 core start address and release the secondary core from holdoff and startup.
   Required properties:
-  - compatible: should be "fsl,ls1021a-dcfg"
+  - compatible: should be "fsl,<chip>-dcfg"
+    Possible compatibles:
+	"fsl,ls1021a-dcfg"
+	"fsl,ls1043a-dcfg"
+	"fsl,ls2080a-dcfg"
   - reg : should contain base address and length of DCFG memory-mapped registers
 
 Example:
-- 
2.7.4

  reply	other threads:[~2016-07-17  2:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17  2:50 [PATCH v11 0/5] soc: fsl: Add initial guts driver Scott Wood
2016-07-17  2:50 ` Scott Wood [this message]
2016-07-17  2:50 ` [PATCH v11 3/5] soc: fsl: add GUTS driver for QorIQ platforms Scott Wood
     [not found] ` <1468723822-30457-1-git-send-email-oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
2016-07-17  2:50   ` [PATCH v11 2/5] dt: bindings: move guts devicetree doc out of powerpc directory Scott Wood
2016-07-17  2:50   ` [PATCH v11 4/5] powerpc/fsl: move mpc85xx.h to include/linux/fsl Scott Wood
2016-07-20 11:24     ` Arnd Bergmann
2016-07-20 18:31       ` Scott Wood
2016-07-20 20:35         ` Arnd Bergmann
2016-07-21 10:26         ` Michael Ellerman
2016-07-21 16:45           ` Scott Wood
     [not found]             ` <1469119526.25630.42.camel-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
2016-07-21 18:34               ` Arnd Bergmann
2016-07-25  6:12             ` Yangbo Lu
2016-07-27  0:38               ` Scott Wood
2016-08-02  5:57                 ` Yangbo Lu
2016-08-02 21:40                   ` Scott Wood
     [not found]                     ` <1470174043.25630.233.camel-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>
2016-08-03  3:33                       ` Yangbo Lu
2016-07-17  2:50 ` [PATCH v11 5/5] powerpc/fsl-pci: Use fsl_guts_get_svr() 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=1468723822-30457-2-git-send-email-oss@buserror.net \
    --to=oss@buserror.net \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=yangbo.lu@nxp.com \
    /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).