From: Nicolin Chen <nicolinc@nvidia.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: <robin.murphy@arm.com>, <will@kernel.org>,
<lpieralisi@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
Ketan Patil <ketanp@nvidia.com>
Subject: Re: IOMMU_FWSPEC_PCI_RC_ATS for SMMUv3 with DT configuration?
Date: Wed, 24 Apr 2024 22:11:48 -0700 [thread overview]
Message-ID: <ZinmFBBdj0zwwJ+p@Asurada-Nvidia> (raw)
In-Reply-To: <Zek6Lu7oAsVKsywE@Asurada-Nvidia>
Hi Jean,
On Wed, Mar 06, 2024 at 07:53:20PM -0800, Nicolin Chen wrote:
> On Mon, Mar 04, 2024 at 09:25:36AM +0000, Jean-Philippe Brucker wrote:
> > > We have a need to enable ATS on a system using Device Tree. Is
> > > there a suggested way or name of DT binding to add?
> >
> > "ats-supported" was acked by Rob:
> >
> > https://lore.kernel.org/linux-iommu/20200311124506.208376-2-jean-philippe@linaro.org/
> >
> > I don't remember why I didn't follow up with that series, probably just
> > the lack of users at the time (Arm SW model was the only ATS
> > implementation). A simpler implementation would be setting the existing
> > fwspec flag:
> > https://jpbrucker.net/git/linux/commit/?h=sva/current&id=4b6d187154557a7c46c9a67c13453d40a03cc078
> I am out of office this week. So I've asked my team mate to
> get that a try.
My team mate verified this patch using a DT configuration.
Would it be possible for you to respin the of_iommu patch?
If yes, please also add his tag:
Tested-by: Ketan Patil <ketanp@nvidia.com>
Thanks!
Nicolin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-04-25 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 22:00 IOMMU_FWSPEC_PCI_RC_ATS for SMMUv3 with DT configuration? Nicolin Chen
2024-03-04 9:25 ` Jean-Philippe Brucker
2024-03-07 3:53 ` Nicolin Chen
2024-04-25 5:11 ` Nicolin Chen [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=ZinmFBBdj0zwwJ+p@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=jean-philippe@linaro.org \
--cc=ketanp@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=robin.murphy@arm.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 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.