RE: [PATCH v5 3/3] ARM: OMAP2+: onenand: prepare for gpmc driver migration

["Mohammed, Afzal" <afzal@xxxxxx>]

Hi Jon,

On Fri, Jun 29, 2012 at 19:45:37, Hunter, Jon wrote:
> On 06/29/2012 01:15 AM, Mohammed, Afzal wrote:

> > I have a different opinion, even with the existing code, with the default
> > timings for onenand, Numonyx is working in async mode, reason being that
> > frequency is being obtained with read operation executed in async mode
> > (later based on this frequency, code calculates sync timings & then set
> > to sync mode)
> 
> I don't follow "frequency is being obtained with read operation executed
> in async mode". Can you give a code reference?

In the present code, for sync mode, omap2_onenand_set_sync_mode() invokes
omap2_onenand_set_async_mode() initially, to set onenand & gpmc to async mode,
then invokes omap2_onenand_get_freq() to get frequency, here finding out
frequency from onenand is done by reading relevant onenand register
in async mode.

Regards
Afzal
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html