On Thu, 14 Jun 2012, Jon Hunter wrote: > What does make this a bit more difficult is the function > gpmc_round_ns_to_ticks(). It appears to convert nanoseconds to ticks and > back to nanoseconds. I am guessing to account for some rounding error. I > am curious what impact this function is having on the timing. Ideally > this should be handle in gpmc_cs_set_timings(). I don't have the code in front of me at the moment, nor my old GPMC timing spreadsheet, so this comment may be superfluous. But since kernel arithmetic needs to be in integers, it might be necessary to do some of the timing calculations in picosecond units to avoid roundoff issues. - Paul -- 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
