From: Nicolin Chen <nicolinc@nvidia.com>
To: Ashish Mhetre <amhetre@nvidia.com>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>,
<jgg@ziepe.ca>, <linux-arm-kernel@lists.infradead.org>,
<iommu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v4 2/3] iommu/arm-smmu-v3: Detect Tegra264 erratum
Date: Tue, 7 Jul 2026 16:25:14 -0700 [thread overview]
Message-ID: <ak2K2vhIQSTNAPto@Asurada-Nvidia> (raw)
In-Reply-To: <20260609073204.1760077-3-amhetre@nvidia.com>
On Tue, Jun 09, 2026 at 07:32:03AM +0000, Ashish Mhetre wrote:
> +arm_smmu_erratum_cmd_needs_repeating(struct arm_smmu_device *smmu,
> + struct arm_smmu_cmd *cmd)
> +{
[...]
> + if (!static_branch_unlikely(&arm_smmu_erratum_repeat_tlbi_cfgi_key))
> + return false;
> + if (!(smmu->options & ARM_SMMU_OPT_REPEAT_TLBI_CFGI))
> + return false;
Are they redundant?
Nicolin
next prev parent reply other threads:[~2026-07-07 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 7:32 [PATCH v4 0/3] iommu/arm-smmu-v3: Tegra264 invalidation workaround Ashish Mhetre
2026-06-09 7:32 ` [PATCH v4 1/3] iommu/arm-smmu-v3: Factor out CMDQ batch force-sync conditions Ashish Mhetre
2026-06-09 7:32 ` [PATCH v4 2/3] iommu/arm-smmu-v3: Detect Tegra264 erratum Ashish Mhetre
2026-07-07 23:25 ` Nicolin Chen [this message]
2026-07-08 14:12 ` Ashish Mhetre
2026-07-09 0:52 ` Nicolin Chen
2026-07-09 1:41 ` Nicolin Chen
2026-07-09 9:37 ` Ashish Mhetre
2026-06-09 7:32 ` [PATCH v4 3/3] iommu/arm-smmu-v3: Issue CFGI/TLBI twice on Tegra264 Ashish Mhetre
2026-06-17 3:58 ` [PATCH v4 0/3] iommu/arm-smmu-v3: Tegra264 invalidation workaround Ashish Mhetre
2026-06-17 4:54 ` Nicolin Chen
2026-06-17 8:21 ` Jon Hunter
2026-06-29 4:11 ` Ashish Mhetre
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=ak2K2vhIQSTNAPto@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=amhetre@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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.