public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Detlev Casanova <detlev.casanova@collabora.com>,
	 20250325213303.826925-5-detlev.casanova@collabora.com
Cc: alchark@gmail.com, andrzej.p@collabora.com, cassel@kernel.org,
	 conor+dt@kernel.org, devicetree@vger.kernel.org,
	dmitry.perchanov@intel.com, 	dsimic@manjaro.org,
	ezequiel@vanguardiasur.com.ar, gregkh@linuxfoundation.org,
	 heiko@sntech.de, hverkuil@xs4all.nl,
	jacopo.mondi@ideasonboard.com,
	 jeanmichel.hautbois@ideasonboard.com, jonas@kwiboo.se,
	kernel@collabora.com, 	kieran.bingham@ideasonboard.com,
	krzk+dt@kernel.org, laurent.pinchart@ideasonboard.com,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	 linux-rockchip@lists.infradead.org,
	linux-staging@lists.linux.dev,
	Jianfeng Liu	 <liujianfeng1994@gmail.com>,
	mchehab@kernel.org, naush@raspberrypi.com, 	robh@kernel.org,
	sakari.ailus@linux.intel.com, sebastian.reichel@collabora.com,
		tomi.valkeinen@ideasonboard.com, umang.jain@ideasonboard.com
Subject: Re: [PATCH v4 4/6] media: rockchip: Introduce the rkvdec2 driver
Date: Thu, 19 Jun 2025 11:16:15 -0400	[thread overview]
Message-ID: <a66e3d27ee427710ed3de8ce89fa3aca40dced03.camel@collabora.com> (raw)
In-Reply-To: <5900973.DvuYhMxLoT@trenzalore>

Le jeudi 19 juin 2025 à 10:39 -0400, Detlev Casanova a écrit :
> Hi Jianfeng,
> 
> This patch set is now a  bit outdated. I will soon send a new version that you 
> can find at [1].
> That being said, you may be right. without an iommu, it would panic here 
> (although the iommu should really be used).

Let's make sure to test it in the next series. One should be able to comment out
the mmu node in the DT, and then it should work with CMA transparently.

thanks,
Nicolas

> 
> [1]: https://gitlab.collabora.com/detlev/linux/-/tree/add-vdpu381-and-383-to-rkvdec
> 
> Regards,
> Detlev
> 
> On Thursday, 19 June 2025 05:19:32 EDT Jianfeng Liu wrote:
> > Hi Detlev,
> > 
> > On Tue, 25 Mar 2025 17:22:20 -0400, Detlev Casanova wrote:
> >  >+        case RKVDEC2_ALLOC_SRAM:
> >  >+            virt_addr = (unsigned long)ctx->rcb_bufs[i].cpu;
> >  >+
> >  >+            iommu_unmap(rkvdec->iommu_domain, virt_addr, rcb_size)
> > 
> > I'm testing your patch with ffmpeg patched with v4l2-request patches[1],
> > and I usually
> > 
> > get kernel panic here. After checking rkvdec->iommu_domain before
> > running iommu_unmap,
> > 
> > I can pass fluster ffmpeg v4l2-request test. Here is my patch based on
> > your commit:
> > 
> > 
> > diff --git a/drivers/media/platform/rockchip/rkvdec2/rkvdec2.c
> > b/drivers/media/platform/rockchip/rkvdec2/rkvdec2.c
> > index 75768561399..122bcdcebd4 100644
> > --- a/drivers/media/platform/rockchip/rkvdec2/rkvdec2.c
> > +++ b/drivers/media/platform/rockchip/rkvdec2/rkvdec2.c
> > @@ -681,8 +681,8 @@ static void rkvdec2_free_rcb(struct rkvdec2_ctx *ctx)
> >                  switch (ctx->rcb_bufs[i].type) {
> >                  case RKVDEC2_ALLOC_SRAM:
> >                          virt_addr = (unsigned long)ctx->rcb_bufs[i].cpu;
> > -
> > -                       iommu_unmap(rkvdec->iommu_domain, virt_addr,
> > rcb_size);
> > +                       if (rkvdec->iommu_domain)
> > + iommu_unmap(rkvdec->iommu_domain, virt_addr, rcb_size);
> >                          gen_pool_free(ctx->dev->sram_pool, virt_addr,
> > rcb_size);
> >                          break;
> >                  case RKVDEC2_ALLOC_DMA:
> > 
> > 
> > [1] https://github.com/amazingfate/FFmpeg/commits/n6.1.1-new-patches/
> > 
> > 
> > Best regards,
> > 
> > Jianfeng
> 
> 
> 


  reply	other threads:[~2025-06-19 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9f098eab-7b98-4827-8538-3cab0e8d7c63@gmail.com>
2025-06-19 14:39 ` [PATCH v4 4/6] media: rockchip: Introduce the rkvdec2 driver Detlev Casanova
2025-06-19 15:16   ` Nicolas Dufresne [this message]
2025-03-25 21:22 [PATCH v4 0/6] media: rockchip: Add " Detlev Casanova
2025-03-25 21:22 ` [PATCH v4 4/6] media: rockchip: Introduce the " Detlev Casanova

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=a66e3d27ee427710ed3de8ce89fa3aca40dced03.camel@collabora.com \
    --to=nicolas.dufresne@collabora.com \
    --cc=20250325213303.826925-5-detlev.casanova@collabora.com \
    --cc=alchark@gmail.com \
    --cc=andrzej.p@collabora.com \
    --cc=cassel@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=detlev.casanova@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.perchanov@intel.com \
    --cc=dsimic@manjaro.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=jeanmichel.hautbois@ideasonboard.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel@collabora.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=liujianfeng1994@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=naush@raspberrypi.com \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sebastian.reichel@collabora.com \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=umang.jain@ideasonboard.com \
    /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