Hi Tony, On Thu, Jun 14, 2012 at 22:23:37, Tony Lindgren wrote: > Sounds like the tusb6010 non-ns tick value is the only remaining > issue. t.clk_activation = gpmc_ticks_to_ns(1); was used so that gpmc_cs_set_timings would do gpmc_ns_to_ticks over it & hence effectively 1 tick would get programmed in the register for clock activation. A value of 1 for clk_activation also should work due to rounding effect. But I am unable to find reason for failure upon using gpmc_ticks_to_ns(1), which seems to me right thing to be used. Let me try to invoke tusb6010 functions in beagle board, observe timings so that at least I will get an idea what is going on here (even though it is guaranteed to crash) Regards Afzal -- 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
