omap: iommu migration, relocation and cleanups
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest0 of 7 patches 0 repliesNew
Patches in v2 No applies recorded yet
None of the 7 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Tony Lindgren |
|---|---|
| Series | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/7] omap: iommu migration, relocation and cleanups
Quoted 10 lines · Ohad Ben-Cohen
1. Migrate OMAP's iommu driver to the generic IOMMU API, and move it to the dedicated iommu folder.
2. Fix omap3isp appropriately so it doesn't break.
3. Adapt OMAP's iovmm appropriately as well, because omap3isp still relies on it. The plan is eventually to remove iovmm and replace it with the upcoming IOMMU-based generic DMA-API. Move iovmm to the iommu folder too; it belongs there more than it belongs in the OMAP folders.
Quoted 6 lines
4. Start cleaning up OMAP's iommu components towards the end goal, where
1) omap-iommu no longer exports public API (and instead provides its entire functionality via the generic IOMMU API).
2) omap-iovmm is removed.Tested on OMAP3 (with omap3isp) and OMAP4 (with rpmsg/remoteproc).
Glad to see this, thanks for doing this! For all the patches: