All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Nicolin Chen <nicolinc@nvidia.com>
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: Mon, 4 Mar 2024 09:25:36 +0000	[thread overview]
Message-ID: <20240304092536.GA1730174@myrica> (raw)
In-Reply-To: <ZeJP6CwrZ2FSbTYm@Asurada-Nvidia>

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,
Jean


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-03-04  9:25 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 [this message]
2024-03-07  3:53   ` Nicolin Chen
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=20240304092536.GA1730174@myrica \
    --to=jean-philippe@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=nicolinc@nvidia.com \
    --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.