From: Joerg Roedel <joro@8bytes.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: will@kernel.org, laurent.pinchart@ideasonboard.com,
mchehab@kernel.org, andersson@kernel.org,
mathieu.poirier@linaro.org, hns@goldelico.com, b-padhi@ti.com,
andreas@kemnade.info, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-media@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 0/4] Fix omap-iommu bitrot
Date: Wed, 30 Oct 2024 10:55:34 +0100 [thread overview]
Message-ID: <ZyIClriScBy4s6LX@8bytes.org> (raw)
In-Reply-To: <cover.1730136799.git.robin.murphy@arm.com>
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,
hardware is 10+ years out of production, no? So who is still using this
hardware with recent kernels for other purposes than kernel testing?
> 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.
Regards,
Joerg
next prev parent reply other threads:[~2024-10-30 9:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 17:58 [PATCH 0/4] Fix omap-iommu bitrot Robin Murphy
2024-10-28 17:58 ` [PATCH 1/4] remoteproc/omap: Handle ARM dma_iommu_mapping Robin Murphy
2024-12-06 17:00 ` Mathieu Poirier
2024-10-28 17:58 ` [PATCH 2/4] media: omap3isp: " Robin Murphy
2025-02-15 6:57 ` Sicelo
2025-02-15 19:43 ` Laurent Pinchart
2025-02-16 10:27 ` Sakari Ailus
2024-10-28 17:58 ` [PATCH 3/4] iommu/omap: Add minimal fwnode support Robin Murphy
2024-10-28 17:58 ` [PATCH 4/4] iommu: Make bus_iommu_probe() static Robin Murphy
2024-10-28 20:46 ` [PATCH 0/4] Fix omap-iommu bitrot H. Nikolaus Schaller
2024-10-28 22:56 ` Mathieu Poirier
2024-10-29 17:07 ` Kevin Hilman
2024-10-30 4:55 ` Beleswar Prasad Padhi
2024-10-30 9:55 ` Joerg Roedel [this message]
2024-10-30 11:20 ` H. Nikolaus Schaller
2024-10-30 12:38 ` Joerg Roedel
2024-10-30 13:28 ` Sicelo
2024-10-30 23:49 ` Adam Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZyIClriScBy4s6LX@8bytes.org \
--to=joro@8bytes.org \
--cc=andersson@kernel.org \
--cc=andreas@kemnade.info \
--cc=b-padhi@ti.com \
--cc=hns@goldelico.com \
--cc=iommu@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mchehab@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.