[<prev] [next>] [day] [month] [year] [list]
Message-ID: <3ce233c6-0549-41bb-a417-3f66cc707cfa@CH1EHSMHS043.ehs.local>
Date: Fri, 18 Apr 2014 01:28:40 +0530
From: Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@...inx.com>
To: <robh+dt@...nel.org>, <pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<rob@...dley.net>, <michal.simek@...inx.com>,
<grant.likely@...aro.org>, <gregkh@...uxfoundation.org>,
<jason@...edaemon.net>, <ezequiel.garcia@...e-electrons.com>,
<arnd@...db.de>, <dwmw2@...radead.org>,
<computersforpeace@...il.com>, <artem.bityutskiy@...ux.intel.com>,
<pekon@...com>, <jussi.kivilinna@....fi>, <acourbot@...dia.com>,
<ivan.khoronzhuk@...com>, <joern@...fs.org>
CC: <devicetree@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
<kpc528@...il.com>, <kalluripunnaiahchoudary@...il.com>,
Punnaiah Choudary Kalluri <punnaia@...inx.com>
Subject: [PATCH RFC v2 4/4] mtd: nand: Add a devicetree binding for onfi timing parameters
Added binding information for onfi timing parameters as per the
onfi 1.0 specification. So, nand controllers that have support for
configuring any of these timing parameters can use this binding
information.
Signed-off-by: Punnaiah Choudary Kalluri <punnaia@...inx.com>
---
Documentation/devicetree/bindings/mtd/nand.txt | 46 ++++++++++++++++++++++++
1 files changed, 46 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/mtd/nand.txt b/Documentation/devicetree/bindings/mtd/nand.txt
index b53f92e..4901091 100644
--- a/Documentation/devicetree/bindings/mtd/nand.txt
+++ b/Documentation/devicetree/bindings/mtd/nand.txt
@@ -19,3 +19,49 @@ errors per {size} bytes".
The interpretation of these parameters is implementation-defined, so not all
implementations must support all possible combinations. However, implementations
are encouraged to further specify the value(s) they support.
+
+Timing parameters:
+ Based on onfi specification 1.0, following are defined parameters.Each
+controller should add supported parameters to IP node.
+All the timing parameters are in nano second time units.
+
+- nand-tADL-ns : ALE to data loading time
+- nand-tALH-ns : ALE hold time
+- nand-tALS-ns : ALE setup time
+- nand-tAR-ns : ALE to RE# delay
+- nand-tBERS-ns : Block erase time
+- nand-tCEA-ns : CE# access time
+- nand-tCCS-ns : Change column setup time
+- nand-tCH-ns : CE# hold time
+- nand-tCHZ-ns : CE# high to output hi-Z
+- nand-tCLH-ns : CLE hold time
+- nand-tCLR-ns : CLE to RE# delay
+- nand-tCLS-ns : CLE setup time
+- nand-tCOH-ns : CE# high to output hold
+- nand-tCS-ns : CE# setup time
+- nand-tDH-ns : Data hold time
+- nand-tDS-ns : Data setup time
+- nand-tFEAT-ns : Busy time for Set Features and Get Features
+- nand-tIEBSY-ns : Busy time for interleaved erase operation
+- nand-tIPBSY-ns : Busy time for interleaved program operation
+- nand-tIR-ns : Output hi-Z to RE# low
+- nand-tPCBSY-ns : Program cache busy time
+- nand-tPROG-ns : Page program time
+- nand-tR-ns : Page read time
+- nand-tRC-ns : RE# cycle time
+- nand-tRCBSY-ns : Read cache busy time
+- nand-tREA-ns : RE# access time
+- nand-tREH-ns : RE# high hold time
+- nand-tRHOH-ns : RE# high to output hold
+- nand-tRHW-ns : RE# high to WE# low
+- nand-tRHZ-ns : RE# high to output hi-z
+- nand-tRLOH-ns : RE# low to output hold
+- nand-tRP-ns : RE# pulse width
+- nand-tRR-ns : Ready to RE# low
+- nand-tRST-ns : Device reset time
+- nand-tWB-ns : WE# high to R/B# low
+- nand-tWC-ns : WE# cycle time
+- nand-tWH-ns : WE# high hold time
+- nand-tWHR-ns : WE# high to RE# low
+- nand-tWP-ns : WE# pulse width
+- nand-tWW-ns : WP# transition to WE# low
--
1.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists