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>
Subject: Re: IOMMU_FWSPEC_PCI_RC_ATS for SMMUv3 with DT configuration?
Date: Wed, 6 Mar 2024 19:53:18 -0800 [thread overview]
Message-ID: <Zek6Lu7oAsVKsywE@Asurada-Nvidia> (raw)
In-Reply-To: <20240304092536.GA1730174@myrica>
Hi Jean,
On Mon, Mar 04, 2024 at 09:25:36AM +0000, Jean-Philippe Brucker wrote:
> Hi,
>
> On Fri, Mar 01, 2024 at 02:00:08PM -0800, Nicolin Chen wrote:
> > Hi all.
> >
> > Currently, the SMMUv3 driver relies on IOMMU_FWSPEC_PCI_RC_ATS
> > in arm_smmu_ats_supported(). This flag seems to be only set in
> > the drivers/acpi/arm64/iort.c file, which does not work for DT
> > configuration.
> >
> > 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
Thanks for the reply and links!
I am out of office this week. So I've asked my team mate to
get that a try.
Thank you
Nicolin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-07 3:54 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 [this message]
2024-04-25 5:11 ` Nicolin Chen
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=Zek6Lu7oAsVKsywE@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=jean-philippe@linaro.org \
--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 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).