Re: [patch 2.6.18-omap] omap2/gpmc updates

[David Brownell <david-b@pacbell.net>]

On Thursday 19 October 2006 12:15 am, Timo Teras wrote:
> On Wed, Oct 18, 2006 at 01:42:14PM -0700, David Brownell wrote:
> > Note that this API is glitchy; likely the best fix would be to add
> > a member to "struct gpmc_timings" to hold GPMC_CONFIG1, since that
> > holds one key aspect of the GPMC timings (the gpmc_fclk divisor,
> > and sync vs. async == whether that divisor matters).
> 
> Something like that would be useful. 

More of a cleanup IMO.  But one of several that seems needed.  :)


> Also currently you can only calculate 
> the timings in nanosecond precision. This is not enough in some cases
> e.g. when calculating sync. timings and the tick length is not multiple of
> nanosecond. We need picosecond precision or the possiblity to configure
> ticks directly.

Right now I'm working with an H4 board where those timings come out
neatly ... multiples of 10 nsec.  Agreed that there are situations
where the numbers aren't so neat.  Of course there aren't _yet_ any
examples of code needing/using those GPMC calls in the tree ...

- Dave