+ Sekhar.
Hi Pekon,
On 09/03/2014 08:29 PM, pekon wrote:
Hi Roger,
On Wednesday 03 September 2014 02:02 PM, Roger Quadros wrote:
Hi Pekon,
On 09/02/2014 10:02 PM, pekon wrote:
Hi Roger,
On Tuesday 02 September 2014 07:27 PM, Roger Quadros wrote:
NAND uses wait pin only to indicate
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)
Hi Pekon,
On 09/02/2014 10:02 PM, pekon wrote:
Hi Roger,
On Tuesday 02 September 2014 07:27 PM, Roger Quadros wrote:
NAND uses wait pin only to indicate device readiness after
a block/page operation. It is not use to extend individual
read/write cycle and so read/write wait pin
Hi Roger,
On Wednesday 03 September 2014 02:02 PM, Roger Quadros wrote:
Hi Pekon,
On 09/02/2014 10:02 PM, pekon wrote:
Hi Roger,
On Tuesday 02 September 2014 07:27 PM, Roger Quadros wrote:
NAND uses wait pin only to indicate device readiness after
a block/page operation. It is not use to
NAND uses wait pin only to indicate device readiness after
a block/page operation. It is not use to extend individual
read/write cycle and so read/write wait pin monitoring must
be disabled for NAND.
This patch also gets rid of the below warning when NAND is
accessed for the first time.
Hi Roger,
On Tuesday 02 September 2014 07:27 PM, Roger Quadros wrote:
NAND uses wait pin only to indicate device readiness after
a block/page operation. It is not use to extend individual
read/write cycle and so read/write wait pin monitoring must
be disabled for NAND.
I think this is