> Am 30.10.2024 um 10:55 schrieb Joerg Roedel <joro@xxxxxxxxxx>: > > On Mon, Oct 28, 2024 at 05:58:34PM +0000, Robin Murphy wrote: >> It seems omap-iommu hasn't had enough mainline users to avoid bitrotting >> through the more recent evolution of the IOMMU API internals. These >> patches attempt to bring it and its consumers sufficiently up-to-date >> to work again, in a manner that's hopefully backportable. This is >> largely all written by inspection, but I have managed to lightly boot >> test patch #3 on an OMAP4 Pandaboard to confirm iommu_probe_device() >> working again. > > My initial reflex would have been to just wipe the omap drivers, Why that? There was a discussion and everyone agreed to remove omap2, but not omap3 and later. > hardware is 10+ years out of production, no? So who is still using this > hardware with recent kernels for other purposes than kernel testing? There are some devices besides the PandaBoard. I am aware of these where this is relevant: Epson BT200, Samsung Galaxy Tab 2, Pyra Handheld (in production) and we are currently thinking about producing a tiny series of the DM3730 based GTA04A5 with spare parts. And of course we want to participate from the latest and greatest upstream changes. > >> This supersedes my previous patch[1]. Patches #1 and #2 are functionally >> independent, and can be applied directly to their respective trees if >> preferred. > > I applied patches 3 and 4 to the ti/omap branch. Thanks, Nikolaus
