From: pekon <pekon@pek-sem.com>
To: Roger Quadros <rogerq@ti.com>
Cc: tony@atomide.com, linux-mtd <linux-mtd@lists.infradead.org>,
linux-omap@vger.kernel.org, "Nori, Sekhar" <nsekhar@ti.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: [PATCH 3/6] ARM: dts: am437x-gp-evm: Don't use read/write wait monitoring
Date: Fri, 05 Sep 2014 00:27:45 +0530 [thread overview]
Message-ID: <5408B629.4030404@pek-sem.com> (raw)
In-Reply-To: <540834F9.8080902@ti.com>
On Thursday 04 September 2014 03:16 PM, Roger Quadros wrote:
[...]
>
> This patch is for the 3.17 bug fix cycle. Implementing NAND device ready mechanism
> is a new feature (for DT case) and I will work on it for future versions.
>
> Also I'm not de-scoping wait-pin (or more correctly device ready) mechanism for NAND.
> The dts file still contains "wait-pin = <0>" property. This will be used to
> monitor the NAND device ready status via GPMC status or GPMC interrupt.
> But this is not for 3.17 bug fix cycle.
>
Ok Thanks, that good to know. So for this whole series
Reviewed-by: Pekon Gupta <pekon@pek-sem.com>
with regards, pekon
------------------------
Powered by BigRock.com
prev parent reply other threads:[~2014-09-04 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1409666227-20622-1-git-send-email-rogerq@ti.com>
[not found] ` <1409666227-20622-4-git-send-email-rogerq@ti.com>
2014-09-02 19:02 ` [PATCH 3/6] ARM: dts: am437x-gp-evm: Don't use read/write wait monitoring pekon
2014-09-03 8:32 ` Roger Quadros
2014-09-03 17:29 ` pekon
2014-09-04 9:46 ` Roger Quadros
2014-09-04 18:57 ` pekon [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=5408B629.4030404@pek-sem.com \
--to=pekon@pek-sem.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rogerq@ti.com \
--cc=tony@atomide.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