omap3: Optimize detection of cpu revision
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 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.
Cover letter [U-Boot] [PATCH 0/2] omap3: Optimize detection of cpu revision
Quoted 12 lines · Sanjeev Premi
Each call to
get_cpu_rev()leads to repetitive execution of code to detect the cpu revision.This patchset ensures that mechanism to detect revision is not executed each time; instead a stored value is returned.
Since, revision info is needed in
s_init(), the function to identify cpu revision needs to be called twice. At the moment, it is necessary/ unavoidable.
Is there some other reason to read this register only once? This function is not used frequently and i do not think the complexity of optimizing is necessary.
Tom