From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sicelo <absicsz@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
joro@8bytes.org, will@kernel.org, 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,
Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [PATCH 2/4] media: omap3isp: Handle ARM dma_iommu_mapping
Date: Sat, 15 Feb 2025 21:43:28 +0200 [thread overview]
Message-ID: <20250215194328.GF12632@pendragon.ideasonboard.com> (raw)
In-Reply-To: <Z7A61N13dZpu53xI@tp440p.steeds.sam>
CC'ing Sakari.
Sakari, would you pick this patch ?
On Sat, Feb 15, 2025 at 08:57:24AM +0200, Sicelo wrote:
> On Mon, Oct 28, 2024 at 05:58:36PM +0000, Robin Murphy wrote:
> > It's no longer practical for the OMAP IOMMU driver to trick
> > arm_setup_iommu_dma_ops() into ignoring its presence, so let's use the
> > same tactic as other IOMMU API users on 32-bit ARM and explicitly kick
> > the arch code's dma_iommu_mapping out of the way to avoid problems.
> >
> > Fixes: 4720287c7bf7 ("iommu: Remove struct iommu_ops *iommu from arch_setup_dma_ops()")
> > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> > ---
> > drivers/media/platform/ti/omap3isp/isp.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/drivers/media/platform/ti/omap3isp/isp.c b/drivers/media/platform/ti/omap3isp/isp.c
> > index 91101ba88ef0..b2210841a320 100644
> > --- a/drivers/media/platform/ti/omap3isp/isp.c
> > +++ b/drivers/media/platform/ti/omap3isp/isp.c
> > @@ -1961,6 +1961,13 @@ static int isp_attach_iommu(struct isp_device *isp)
> > struct dma_iommu_mapping *mapping;
> > int ret;
> >
> > + /* We always want to replace any default mapping from the arch code */
> > + mapping = to_dma_iommu_mapping(isp->dev);
> > + if (mapping) {
> > + arm_iommu_detach_device(isp->dev);
> > + arm_iommu_release_mapping(mapping);
> > + }
> > +
> > /*
> > * Create the ARM mapping, used by the ARM DMA mapping core to allocate
> > * VAs. This will allocate a corresponding IOMMU domain.
> > --
> > 2.39.2.101.g768bb238c484.dirty
> >
>
> I have finally found time to test this patch on the Nokia N900 and can
> confirm it is working fine.
>
> I was wondering - is there a reason that it is not merged yet? I tested
> on 6.14-rc2, which did not have it, and notice it is also not in
> linux-next.
>
> If it helps:
>
> Tested-by: Sicelo A. Mhlongo <absicsz@gmail.com>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-02-15 19:45 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 [this message]
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
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=20250215194328.GF12632@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=absicsz@gmail.com \
--cc=andersson@kernel.org \
--cc=andreas@kemnade.info \
--cc=b-padhi@ti.com \
--cc=hns@goldelico.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--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=sakari.ailus@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).