[PATCH 0/4] OMAP-GPMC generic timing migration
x0148406 at ti.com
Thu Oct 18 01:26:13 EDT 2012
On Wednesday 17 October 2012 08:43 PM, Daniel Mack wrote:
> On 17.10.2012 07:42, Afzal Mohammed wrote:
>> I doubt whether auxdata would help here, it seems using
>> compatible field alone would help in deciding relevant
>> custom timing routine. Whether we want this kind of
>> peripheral knowledge in gpmc driver instead of using
>> generic timing routine has to be decided though.
> Another thing that might be worth thinking about is that apart from the
> GPMC host controller and the peripherals, there could be other
> components like level shifters or series resistors on the board that
> limit the maximum speed of transactions. So in fact we might be better
> off storing all that timing details in the DT, as they are in fact
> highly application specific.
Yes, making it future proof for these kind of scenarios was one
of the reason's that initially triggered generic timing path.
More information about the linux-arm-kernel