All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Bingbu Cao <bingbu.cao@linux.intel.com>
Cc: linux-media@vger.kernel.org,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Bingbu Cao <bingbu.cao@intel.com>
Subject: Re: [PATCH] media: intel/ipu6: Fix dma mask for non-secure mode
Date: Thu, 10 Apr 2025 10:52:19 +0200	[thread overview]
Message-ID: <Z/eGw6D5aZ5WAqaJ@linux.intel.com> (raw)
In-Reply-To: <57590fee-9f62-8776-1597-6e125daafe58@linux.intel.com>

Hi Bingbu,

On Thu, Apr 10, 2025 at 02:53:45PM +0800, Bingbu Cao wrote:
> Stanislaw,
> 
> Thanks for the patch.
> 
> On 4/9/25 5:58 PM, Stanislaw Gruszka wrote:
> > We use dma_get_mask() of auxdev device for calculate iova pfn limit.
> > This is always 32 bit mask as we do not initialize the mask (and we can
> > not do so, since dev->dev_mask is NULL anyways for auxdev).
> 
> Indeed.
> 
> > 
> > Since we need 31 bit mask for non-secure mode create wrapper of
> > alloc_iova() which use mmu_info->aperture_end. This give us always
> > the correct mask.
> > 
> > Fixes: daabc5c64703 ("media: ipu6: not override the dma_ops of device in driver")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> > ---
> >  drivers/media/pci/intel/ipu6/ipu6-dma.c |  6 ++----
> >  drivers/media/pci/intel/ipu6/ipu6-dma.h |  7 -------
> >  drivers/media/pci/intel/ipu6/ipu6-mmu.c |  3 +--
> >  drivers/media/pci/intel/ipu6/ipu6-mmu.h | 13 +++++++++++++
> >  4 files changed, 16 insertions(+), 13 deletions(-)
> > 
> > diff --git a/drivers/media/pci/intel/ipu6/ipu6-dma.c b/drivers/media/pci/intel/ipu6/ipu6-dma.c
> > index b34022bad83b..a1d4ec35f802 100644
> > --- a/drivers/media/pci/intel/ipu6/ipu6-dma.c
> > +++ b/drivers/media/pci/intel/ipu6/ipu6-dma.c
> > @@ -171,8 +171,7 @@ void *ipu6_dma_alloc(struct ipu6_bus_device *sys, size_t size,
> >  	size = PAGE_ALIGN(size);
> >  	count = PHYS_PFN(size);
> >  
> > -	iova = alloc_iova(&mmu->dmap->iovad, count,
> > -			  PHYS_PFN(dma_get_mask(dev)), 0);
> 
> How about directly call?
> 	iova = alloc_iova(&mmu->dmap->iovad, count,
> 			  PHYS_PFN(mmu->dmap->mmu_info->aperture_end), 0);
> 
> Less change, better.

Yes, direct call results in smaller/nicer fix, I will do this in v2.

Regards
Stanislaw

      reply	other threads:[~2025-04-10  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09  9:58 [PATCH] media: intel/ipu6: Fix dma mask for non-secure mode Stanislaw Gruszka
2025-04-09 10:20 ` Stanislaw Gruszka
2025-04-09 12:20 ` kernel test robot
2025-04-09 13:14 ` kernel test robot
2025-04-10  6:53 ` Bingbu Cao
2025-04-10  8:52   ` Stanislaw Gruszka [this message]

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=Z/eGw6D5aZ5WAqaJ@linux.intel.com \
    --to=stanislaw.gruszka@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.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 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.