[PATCH] fsl_ifc_nand: Added random output enable cmd

[Prabhakar Kushwaha]

Hi Scott,

Sorry for very late reply.

> -----Original Message-----
> From: Scott Wood [mailto:oss at buserror.net]
> Sent: Thursday, September 08, 2016 5:01 AM
> To: Boris Brezillon <boris.brezillon at free-electrons.com>; Ronak Desai
> <ronak.desai at rockwellcollins.com>
> Cc: Matt Weber <matthew.weber at rockwellcollins.com>; Prabhakar Kushwaha
> <prabhakar.kushwaha at nxp.com>; linux-mtd at lists.infradead.org; Ezequiel
> Garcia <ezequiel at vanguardiasur.com.ar>
> Subject: Re: [PATCH] fsl_ifc_nand: Added random output enable cmd
> 
> On Wed, 2016-09-07 at 18:15 +0200, Boris Brezillon wrote:
> > On Wed, 7 Sep 2016 09:50:50 -0500
> > Ronak Desai <ronak.desai at rockwellcollins.com> wrote:
> >
> > > IFC input clock is divide by 2 platform clock which is fixed in T, P
> > > series
> > > and Layerscape series of processors where IFC is used, maximum
> > > platform clock is 600 MHz so IFC input clock becomes 300 MHz maximum.
> > > To avoid floating operation, I chose next possible frequency of
> > > 333.33 MHz which gives me period of 3 ns. There was no easy way to find
> > > the input IFC clock without knowing platform clock which requires RCW
> > > values.
> > > So, to avoid that I selected this route where we will end up waiting few
> > > more
> > > cycles then required but it does not harm. For example, my input IFC clock
> > > is
> > > 266.66 Mhz and my NAND part tells me to wait minimum 200 ns so I have to
> > > wait for  54 cycles while with this calculation I will be waiting for 66
> > > cycles
> > > which I think won't matter as the data-sheet specifies minimum change
> > > column
> > > set-up time.
> > Ok, let's forget this aspect for now. It just feels weird for someone
> > who is working on ARM platforms to see code that is making assumptions
> > on the parent clk rate.
> > We usually have most clocks exposed through the clk framework, and
> > query the rate of the clock driving the IP before calculating
> > sub-timings.
> 
> I don't like seeing these assumptions hardcoded either, and we do have a clock
> driver that can supply this information.  We just need to add an appropriate
> clocks property to the IFC node (though the driver should keep working at
> least as well as it currently does on existing device trees).
> 
> Prabhakar, do you know of a FIR operation other than NWAIT that would be
> suitable here if we do go the route of sending a real RNDOUT command?

There is no FIR operation other than NWAIT which can be used. 
Same has been confirmed from design team. 

--prabhakar