From: Jason Gunthorpe <jgg@nvidia.com>
To: Stanimir Varbanov <svarbanov@suse.de>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Dmitry Osipenko <digetx@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
linux-media@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-arm-msm@vger.kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] media: venus: firmware: Use iommu_paging_domain_alloc()
Date: Fri, 6 Sep 2024 10:20:48 -0300 [thread overview]
Message-ID: <20240906132048.GD1358970@nvidia.com> (raw)
In-Reply-To: <d6d5490e-7270-4391-b91a-72af551c6e7d@suse.de>
On Fri, Sep 06, 2024 at 12:51:08PM +0300, Stanimir Varbanov wrote:
> >> On 12.08.24 г. 10:21 ч., Lu Baolu wrote:
> >>> An iommu domain is allocated in venus_firmware_init() and is attached to
> >>> core->fw.dev in the same function. Use iommu_paging_domain_alloc() to
> >>> make it explicit.
> >>>
> >>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> >>> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> >>> Link: https://lore.kernel.org/r/20240610085555.88197-10-baolu.lu@linux.intel.com
> >>> ---
> >>> drivers/media/platform/qcom/venus/firmware.c | 6 +++---
> >>> 1 file changed, 3 insertions(+), 3 deletions(-)
> >>>
> >>> diff --git a/drivers/media/platform/qcom/venus/firmware.c b/drivers/media/platform/qcom/venus/firmware.c
> >>> index fe7da2b30482..66a18830e66d 100644
> >>> --- a/drivers/media/platform/qcom/venus/firmware.c
> >>> +++ b/drivers/media/platform/qcom/venus/firmware.ced
> >>
> >> Acked-by: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>
> >>
> >> I'll take the patch through linux-media tree.
> >
> > Did this patch and the 1/2:
>
> 2/2 is in linux-next now.
And 1/2? Can someone pick it up too?
https://lore.kernel.org/all/2o6gpxknio4kvf5fmqgai5jaov65semmw3wvtmt4gdauwzhbti@ii3ydtlmp2sb/
Thanks,
Jason
next prev parent reply other threads:[~2024-09-06 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 7:21 [PATCH 1/2] media: nvidia: tegra: Use iommu_paging_domain_alloc() Lu Baolu
2024-08-12 7:21 ` [PATCH 2/2] media: venus: firmware: " Lu Baolu
2024-08-20 20:43 ` Stanimir Varbanov
2024-09-04 12:16 ` Jason Gunthorpe
2024-09-06 9:51 ` Stanimir Varbanov
2024-09-06 13:20 ` Jason Gunthorpe [this message]
2024-08-29 15:25 ` [PATCH 1/2] media: nvidia: tegra: " Thierry Reding
2024-09-15 14:08 ` Jason Gunthorpe
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=20240906132048.GD1358970@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=digetx@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=iommu@lists.linux.dev \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_vgarodia@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=stanimir.k.varbanov@gmail.com \
--cc=svarbanov@suse.de \
--cc=thierry.reding@gmail.com \
--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