From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: Robin Murphy <robin.murphy@arm.com>, <joro@8bytes.org>,
<will@kernel.org>, <laurent.pinchart@ideasonboard.com>,
<mchehab@kernel.org>, <andersson@kernel.org>,
<mathieu.poirier@linaro.org>
Cc: <hns@goldelico.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>, Andrew Davis <afd@ti.com>,
Udit Kumar <u-kumar1@ti.com>, "Nagalla, Hari" <hnagalla@ti.com>
Subject: Re: [PATCH 0/4] Fix omap-iommu bitrot
Date: Wed, 30 Oct 2024 10:25:37 +0530 [thread overview]
Message-ID: <25c5c744-2e4d-4df6-a080-8f5705a47884@ti.com> (raw)
In-Reply-To: <cover.1730136799.git.robin.murphy@arm.com>
Hi Robin,
On 28/10/24 23:28, Robin Murphy wrote:
> Hi all,
>
> 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.
>
> This supersedes my previous patch[1]. Patches #1 and #2 are functionally
> independent, and can be applied directly to their respective trees if
> preferred.
>
> Thanks,
> Robin.
>
> [1] https://lore.kernel.org/linux-iommu/c44545c6d07c65d89daa297298c27bb0f15c8b84.1728393458.git.robin.murphy@arm.com/
>
>
> Robin Murphy (4):
> remoteproc/omap: Handle ARM dma_iommu_mapping
> media: omap3isp: Handle ARM dma_iommu_mapping
> iommu/omap: Add minimal fwnode support
> iommu: Make bus_iommu_probe() static
Tested this series on omap4 w.r.t. remoteproc subsystem on v6.12-rc5, it
works fine; attached logs[2]. Therefore, for series please use:
Tested-by: Beleswar Padhi <b-padhi@ti.com>
Many thanks for working on the fix.
Best,
Beleswar
[2]: https://gist.github.com/3V3RYONE/f9244a0aa0e3514b7c62f7965cbb0bae
>
> drivers/iommu/iommu.c | 3 ++-
> drivers/iommu/omap-iommu.c | 26 +++++++++++++++---------
> drivers/media/platform/ti/omap3isp/isp.c | 7 +++++++
> drivers/remoteproc/omap_remoteproc.c | 17 ++++++++++++++++
> include/linux/iommu.h | 1 -
> 5 files changed, 42 insertions(+), 12 deletions(-)
>
next prev parent reply other threads:[~2024-10-30 4:56 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 [this message]
2024-10-30 9:55 ` Joerg Roedel
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=25c5c744-2e4d-4df6-a080-8f5705a47884@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=andreas@kemnade.info \
--cc=hnagalla@ti.com \
--cc=hns@goldelico.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--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=u-kumar1@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox