From: Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@xilinx.com>
To: <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <rob@landley.net>,
<michal.simek@xilinx.com>, <grant.likely@linaro.org>,
<gregkh@linuxfoundation.org>, <jason@lakedaemon.net>,
<ezequiel.garcia@free-electrons.com>, <arnd@arndb.de>,
<dwmw2@infradead.org>, <computersforpeace@gmail.com>,
<artem.bityutskiy@linux.intel.com>, <pekon@ti.com>,
<jussi.kivilinna@iki.fi>, <acourbot@nvidia.com>,
<ivan.khoronzhuk@ti.com>, <joern@logfs.org>
Cc: <devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
<kpc528@gmail.com>, <kalluripunnaiahchoudary@gmail.com>,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>
Subject: [PATCH RFC v2 4/4] mtd: nand: Add a devicetree binding for onfi timing parameters
Date: Fri, 18 Apr 2014 01:28:40 +0530 [thread overview]
Message-ID: <3ce233c6-0549-41bb-a417-3f66cc707cfa@CH1EHSMHS043.ehs.local> (raw)
In-Reply-To: <1397764720-29846-1-git-send-email-punnaia@xilinx.com>
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@xilinx.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
prev parent reply other threads:[~2014-04-17 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1397764720-29846-1-git-send-email-punnaia@xilinx.com>
2014-04-17 19:58 ` [PATCH RFC v2 1/4] Devicetree: Add pl353 smc controller devicetree binding information Punnaiah Choudary Kalluri
2014-04-17 19:58 ` [PATCH RFC v2 2/4] memory: pl353: Add driver for arm pl353 static memory controller Punnaiah Choudary Kalluri
2014-04-17 19:58 ` [PATCH RFC v2 3/4] nand: pl353: Add driver for arm pl353 smc nand interface Punnaiah Choudary Kalluri
2014-04-17 19:58 ` Punnaiah Choudary Kalluri [this message]
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=3ce233c6-0549-41bb-a417-3f66cc707cfa@CH1EHSMHS043.ehs.local \
--to=punnaiah.choudary.kalluri@xilinx.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=jason@lakedaemon.net \
--cc=joern@logfs.org \
--cc=jussi.kivilinna@iki.fi \
--cc=kalluripunnaiahchoudary@gmail.com \
--cc=kpc528@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=pekon@ti.com \
--cc=punnaia@xilinx.com \
--cc=rob@landley.net \
--cc=robh+dt@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
all inboxes | Powered by JetHome®