Messages in this thread | | | Date | Wed, 25 Feb 2015 17:26:03 +0100 | From | Robert Abel <> | Subject | Re: [PATCH 5/8 v2] ARM OMAP2+ GPMC: change get_gpmc_timing_reg output for DTS |
| |
Hi Tony,
On 25 Feb 2015 16:23, Tony Lindgren wrote: > * Roger Quadros <rogerq@ti.com> [150225 05:28]: >> On 24/02/15 22:05, Robert ABEL wrote: >>> DTS output was formatted to require additional work when copy-pasting into DTS. >>> Nano-second timings were removed, because they were not a confidence interval nor >>> an indication what timing values would result in the same #ticks >> If they were not is it possible to dump min,max timings that will result in >> the same ticks? > Yeah my plan was o display the nanosecond range resulting in the > same tick value. That makes it a bit easier to compare the timings > to the data sheet. So maybe show both tick and ns range? Ah, so my hunch was right. I reimplemented that correctly now. Basically, your code just went [ticks-1, ticks+1] in ns. But times are always ceiling(ns / gpmc_[f]clk), i.e. (ticks - 1, ticks] in ns.
Some other patches change as well because of this change, so a v3 is in order =].
Regards,
Robert
| |