linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
	Russell King <linux@armlinux.org.uk>
Cc: Inki Dae <inki.dae@samsung.com>,
	Seung-Woo Kim <sw0312.kim@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
	iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dma-mapping: Pass device to arm_iommu_create_mapping()
Date: Wed, 4 Sep 2024 09:44:05 -0300	[thread overview]
Message-ID: <20240904124405.GA825382@nvidia.com> (raw)
In-Reply-To: <20240812070202.9366-1-baolu.lu@linux.intel.com>

On Mon, Aug 12, 2024 at 03:02:01PM +0800, Lu Baolu wrote:
> From: Robin Murphy <robin.murphy@arm.com>
> 
> All users of ARM IOMMU mappings create them for a particular device, so
> change the interface to accept the device rather than forcing a vague
> indirection through a bus type. This prepares for making a similar
> change to iommu_domain_alloc() itself.
> 
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> Link: https://lore.kernel.org/r/20240610085555.88197-17-baolu.lu@linux.intel.com
> ---
>  arch/arm/include/asm/dma-iommu.h         | 2 +-
>  arch/arm/mm/dma-mapping.c                | 8 ++++----
>  drivers/gpu/drm/exynos/exynos_drm_dma.c  | 2 +-
>  drivers/iommu/ipmmu-vmsa.c               | 3 +--
>  drivers/iommu/mtk_iommu_v1.c             | 3 +--
>  drivers/media/platform/ti/omap3isp/isp.c | 2 +-
>  6 files changed, 9 insertions(+), 11 deletions(-)

I still have an account with RMK's patch tracking system, so I went
ahead and put these there so Russell can pick them up:

 https://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=9417/1
 https://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=9418/1

I think I did it right, though it has been a decade since I last did
this..

Regards,
Jason


      parent reply	other threads:[~2024-09-04 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12  7:02 [PATCH 1/2] ARM: dma-mapping: Pass device to arm_iommu_create_mapping() Lu Baolu
2024-08-12  7:02 ` [PATCH 2/2] ARM: dma-mapping: Use iommu_paging_domain_alloc() Lu Baolu
2024-09-04 12:44 ` Jason Gunthorpe [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=20240904124405.GA825382@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=alim.akhtar@samsung.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=krzk@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=robin.murphy@arm.com \
    --cc=sw0312.kim@samsung.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@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;
as well as URLs for NNTP newsgroup(s).