mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Han Xu <han.xu@nxp.com>
To: <shijie.huang@arm.com>, <dwmw2@infradead.org>,
	<computersforpeace@gmail.com>, <han.xu@nxp.com>,
	<standby24x7@gmail.com>, <jkosina@suse.cz>,
	<boris.brezillon@free-electrons.com>,
	<fabio.estevam@freescale.com>, <fransklaver@gmail.com>,
	<hofrat@osadl.org>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 2/5] mtd: nand: gpmi: document the clocks and clock-names in DT property
Date: Tue, 23 Feb 2016 17:04:50 -0600	[thread overview]
Message-ID: <1456268693-8630-3-git-send-email-han.xu@nxp.com> (raw)
In-Reply-To: <1456268693-8630-1-git-send-email-han.xu@nxp.com>

add the clocks and clock-names in DT property, gpmi-io clock is
mandatory for all platforms, but some platforms, such as i.MX6Q may
need more extra clocks for submodules. More details please refer to the
SoC reference manual.

Signed-off-by: Han Xu <han.xu@nxp.com>
---
 Documentation/devicetree/bindings/mtd/gpmi-nand.txt | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Documentation/devicetree/bindings/mtd/gpmi-nand.txt b/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
index d02acaf..c8d0e2f 100644
--- a/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
+++ b/Documentation/devicetree/bindings/mtd/gpmi-nand.txt
@@ -13,6 +13,13 @@ Required properties:
     and GPMI DMA channel ID.
     Refer to dma.txt and fsl-mxs-dma.txt for details.
   - dma-names: Must be "rx-tx".
+  - clocks : The clocks needed by the gpmi controller. This field varies
+    depends on the SoC design, "gpmi-io" is mandatory but some platforms may
+    need several extra clocks, such as i.MX6Q, it requires "gpmi_apb,
+    gpmi_bch, gpmi_bch_apb and per1_bch" for all submodules. Please refer to
+    the HW design manual.
+  - clock-names : the name of the clocks, please refer to the HW design
+    manual.
 
 Optional properties:
   - nand-on-flash-bbt: boolean to enable on flash bbt option if not
@@ -51,6 +58,8 @@ gpmi-nand@8000c000 {
 	interrupt-names = "bch";
 	dmas = <&dma_apbh 4>;
 	dma-names = "rx-tx";
+	clocks = <&clks 50>,;
+	clock-names = "gpmi_io";
 
 	partition@0 {
 	...
-- 
1.9.1

  parent reply	other threads:[~2016-02-23 23:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 23:04 [PATCH 0/5] support gpmi on i.MX6UL/7D and HW bitflip on i.MX6QP/7D Han Xu
2016-02-23 23:04 ` [PATCH 1/5] mtd: nand: gpmi: add GPMI NAND support for i.MX7D Han Xu
2016-04-29  9:01   ` Boris Brezillon
2016-02-23 23:04 ` Han Xu [this message]
2016-04-29  8:50   ` [PATCH 2/5] mtd: nand: gpmi: document the clocks and clock-names in DT property Boris Brezillon
2016-02-23 23:04 ` [PATCH 3/5] mtd: nand: gpmi: correct bitflip for erased NAND page Han Xu
2016-04-29  8:44   ` Boris Brezillon
2016-02-23 23:04 ` [PATCH 4/5] mtd: nand: gpmi: support NAND on i.MX6UL Han Xu
2016-04-29  8:46   ` Boris Brezillon
2016-02-23 23:04 ` [PATCH 5/5] mtd: nand: gpmi: document the new supported chip in DT Han Xu

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=1456268693-8630-3-git-send-email-han.xu@nxp.com \
    --to=han.xu@nxp.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=fabio.estevam@freescale.com \
    --cc=fransklaver@gmail.com \
    --cc=hofrat@osadl.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shijie.huang@arm.com \
    --cc=standby24x7@gmail.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

Powered by JetHome