From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
linux-media@vger.kernel.org
Cc: 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 14:53:45 +0800 [thread overview]
Message-ID: <57590fee-9f62-8776-1597-6e125daafe58@linux.intel.com> (raw)
In-Reply-To: <20250409095825.1014521-1-stanislaw.gruszka@linux.intel.com>
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.
> + iova = ipu6_alloc_iova(mmu, count);
> if (!iova)
> goto out_kfree;
>
> @@ -397,8 +396,7 @@ int ipu6_dma_map_sg(struct ipu6_bus_device *sys, struct scatterlist *sglist,
> dev_dbg(dev, "dmamap trying to map %d ents %zu pages\n",
> nents, npages);
>
> - iova = alloc_iova(&mmu->dmap->iovad, npages,
> - PHYS_PFN(dma_get_mask(dev)), 0);
> + iova = ipu6_alloc_iova(mmu, npages);
> if (!iova)
> return 0;
>
> diff --git a/drivers/media/pci/intel/ipu6/ipu6-dma.h b/drivers/media/pci/intel/ipu6/ipu6-dma.h
> index b51244add9e6..0dd7c0556bd2 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6-dma.h
> +++ b/drivers/media/pci/intel/ipu6/ipu6-dma.h
> @@ -6,8 +6,6 @@
>
> #include <linux/dma-map-ops.h>
> #include <linux/dma-mapping.h>
> -#include <linux/iova.h>
> -#include <linux/iova.h>
> #include <linux/scatterlist.h>
> #include <linux/types.h>
>
> @@ -15,11 +13,6 @@
>
> struct ipu6_mmu_info;
>
> -struct ipu6_dma_mapping {
> - struct ipu6_mmu_info *mmu_info;
> - struct iova_domain iovad;
> -};
> -
> void ipu6_dma_sync_single(struct ipu6_bus_device *sys, dma_addr_t dma_handle,
> size_t size);
> void ipu6_dma_sync_sg(struct ipu6_bus_device *sys, struct scatterlist *sglist,
> diff --git a/drivers/media/pci/intel/ipu6/ipu6-mmu.c b/drivers/media/pci/intel/ipu6/ipu6-mmu.c
> index 6d1c0b90169d..95eb17855847 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6-mmu.c
> +++ b/drivers/media/pci/intel/ipu6/ipu6-mmu.c
> @@ -421,8 +421,7 @@ static int allocate_trash_buffer(struct ipu6_mmu *mmu)
> int ret;
>
> /* Allocate 8MB in iova range */
> - iova = alloc_iova(&mmu->dmap->iovad, n_pages,
> - PHYS_PFN(mmu->dmap->mmu_info->aperture_end), 0);
> + iova = ipu6_alloc_iova(mmu, n_pages);
> if (!iova) {
> dev_err(mmu->dev, "cannot allocate iova range for trash\n");
> return -ENOMEM;
> diff --git a/drivers/media/pci/intel/ipu6/ipu6-mmu.h b/drivers/media/pci/intel/ipu6/ipu6-mmu.h
> index 8e40b4a66d7d..7f3860796762 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6-mmu.h
> +++ b/drivers/media/pci/intel/ipu6/ipu6-mmu.h
> @@ -7,6 +7,7 @@
> #define ISYS_MMID 1
> #define PSYS_MMID 0
>
> +#include <linux/iova.h>
> #include <linux/list.h>
> #include <linux/spinlock_types.h>
> #include <linux/types.h>
> @@ -58,6 +59,11 @@ struct ipu6_mmu {
> void (*tlb_invalidate)(struct ipu6_mmu *mmu);
> };
>
> +struct ipu6_dma_mapping {
> + struct ipu6_mmu_info *mmu_info;
> + struct iova_domain iovad;
> +};
> +
> struct ipu6_mmu *ipu6_mmu_init(struct device *dev,
> void __iomem *base, int mmid,
> const struct ipu6_hw_variants *hw);
> @@ -70,4 +76,11 @@ void ipu6_mmu_unmap(struct ipu6_mmu_info *mmu_info, unsigned long iova,
> size_t size);
> phys_addr_t ipu6_mmu_iova_to_phys(struct ipu6_mmu_info *mmu_info,
> dma_addr_t iova);
> +
> +static inline struct iova *ipu_alloc_iova(struct ipu6_mmu *mmu,
> + unsigned long n_pages)
> +{
> + return alloc_iova(&mmu->dmap->iovad, n_pages,
> + PHYS_PFN(mmu->dmap->mmu_info->aperture_end), 0);
> +}
> #endif
>
--
Best regards,
Bingbu Cao
next prev parent reply other threads:[~2025-04-10 6:58 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 [this message]
2025-04-10 8:52 ` Stanislaw Gruszka
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=57590fee-9f62-8776-1597-6e125daafe58@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stanislaw.gruszka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox