Skip to content

OMAP-GPMC generic timing migration

Afzal Mohammed linux-arm-kernel linux-omap 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 4 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 4 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/4] OMAP-GPMC generic timing migration

Hi Daniel,

Quoted 8 lines · Daniel Mack
Quoted 5 lines · Afzal Mohammed

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.

Quoted 6 lines

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.

Regards
Afzal