Hi Ezequiel, >From: Ezequiel Garcia [mailto:[email protected]] > >Hello Pekon, > >On 16 May 04:33 PM, Pekon Gupta wrote: >[..] >> + gpmc,wait-pin = <0>; >> + gpmc,wait-on-read; >> + gpmc,wait-on-write; > >Thanks for adding the wait-pin property. I think the other boards also >needs this change. Javier, do you have a IGEP Aquila with NAND to try? > >Pekon, have you noticed that there's no devicetree property to enable >ready/busy? In other words, the NAND driver dev_ready field will never >be true when probed from DT. > Yes, that is know, therefore I din't reply to your earlier email. I was just fixing your DT comments and have a small patch to set dev_ready=true. I'll send it soon.
But still you need to consider that nand/omap2.c driver only supports polling way of monitoring READY/BUSY pin. That is instead of polling for status-bit | waiting for predefined delay, NAND driver now polls for READY/BUSY pin. However, actual benefit of wait-pin monitoring might be visible when READY/BUSY pin is used with interrupt. with regards, pekon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
