Skip to content

initialize omap SRAM later on with __arm_ioremap_exec()

Santosh Shilimkar linux-arm-kernel linux-omap 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 of 4 patches 0 repliesNew

3 of 4 patches are in this archive. The cover letter announces 4.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4ARM: Add __arm_ioremap_exec for mapping external memory as MT_MEMORY+0 -07 replies
2/4ARM: OMAP: Avoid cpu_is_omapxxxx usage until map_io is done+0 -00 replies
4/4ARM: OMAP: Map SRAM later on with ioremap_exec()+0 -01 reply

Reviews trailers per patch

2 of 3 patches have a Reviewed-by or Acked-by.

PatchSantosh Shilimkar
1/4
2/4R-b T-b
4/4R-b T-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/4] initialize omap SRAM later on with __arm_ioremap_exec()

Tony,

Quoted 11 lines · Tony Lindgren

Hi all,

Related to the omap static mapping, here's a first take on moving the SRAM init to happen later so we can do generic map_io.

Still working on a similar patch for omap1, will send it a bit later.

Regards,

Tony

Quoted 9 lines

---

Tony Lindgren (4):
ARM: Add __arm_ioremap_exec for mapping external memory as MT_MEMORY
ARM: OMAP: Avoid cpu_is_omapxxxx usage until map_io is done
ARM: OMAP: Remove calls to SRAM allocations for framebuffer
ARM: OMAP: Map SRAM later on with ioremap_exec()

Nice work.

With quick scan, looks like the series will work since you have already taken care of SRAM is being ready before SDRC has been initialised which was the only corner case I was worried.

Will look at this series in next couple of days and do some testing. Looks like you wanted to inlcude below patch also part of this series though [PATCH 5/4] numbering is bit confusing. [PATCH 5/4] ARM: OMAP: Move set_globals initialization to happen in init_early

Regards
Santosh