Hi Jon,
On Mon, Jul 02, 2012 at 22:59:03, Hunter, Jon wrote:
> On 07/02/2012 04:43 AM, Mohammed, Afzal wrote:
> > Not sure whether you are fine with fixing up this patch with added diff
> >
> > Assuming inferences so far is not wrong, right now this patch with the added diff
> > would be perfectly fine.
> >
> > Problem would happen when we are at a stage to do gpmc reset using hwmod [seems
> > miles to go before I sleep {or read gpmc hwmod reset} ;)]. If bootloader left
> > onenand configured in sync mode, to switch onenand to async mode, first configuring
> > gpmc to sync mode would be required & for that we need frequency information
> > from onenand and to get that information from onenand, gpmc has to be configured
> > for sync mode and to configure gpmc to sync mode ....
>
> You are concerned about hwmod performing a reset of the gpmc during
> boot? We should be able to use the HWMOD_INIT_NO_RESET flag to prevent
> this. Would that work?
Yes that will work in the short term, the reason I am trying to avoid no
reset flag in the long term is to prevent this board support being broken,
please refer Paul's requirement [1] in accepting gpmc hwmod patch
Regards
Afzal
[1] http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69041.html
--
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
