public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Jon Hunter <jonathanh@nvidia.com>, Will Deacon <will@kernel.org>,
	Joerg Roedel <joro@8bytes.org>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
	devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Saravana Kannan <saravanak@google.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Yong Wu <yong.wu@mediatek.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v3 2/5] iommu: Resolve fwspec ops automatically
Date: Fri, 12 Jul 2024 16:28:37 +0100	[thread overview]
Message-ID: <82624cf6-98ad-47df-8dcd-368117600805@arm.com> (raw)
In-Reply-To: <ee24cb5f-d170-41d3-9928-5507b8ab22a7@nvidia.com>

On 12/07/2024 4:24 pm, Jon Hunter wrote:
> 
> On 12/07/2024 12:48, Robin Murphy wrote:
> 
> ...
> 
>>> I am seeing some failures on -next with some of our devices. Bisect 
>>> is pointing to this commit. Looks like the host1x device is no longer 
>>> probing successfully. I see the following ...
>>>
>>>   tegra-host1x 50000000.host1x: failed to initialize fwspec: -517
>>>   nouveau 57000000.gpu: failed to initialize fwspec: -517
>>>
>>> The probe seems to be deferred forever. The above is seen on Tegra210 
>>> but Tegra30 and Tegra194 are also having the same problem. 
>>> Interestingly it is not all devices and so make me wonder if we are 
>>> missing something on these devices? Let me know if you have any 
>>> thoughts.
>>
>> Ugh, tegra-smmu has been doing a complete nonsense this whole time - 
>> on closer inspection, it's passing the fwnode of the *client device* 
>> where it should be that of the IOMMU device :(
>>
>> I *think* it should probably just be a case of:
>>
>> -    err = iommu_fwspec_init(dev, of_fwnode_handle(dev->of_node));
>> +    err = iommu_fwspec_init(dev, of_fwnode_handle(smmu->dev->of_node));
>>
>> since smmu->dev appears to be the same one initially passed to 
>> iommu_device_register(), so it at least ought to match and work, but 
>> the SMMU device vs. MC device thing leaves me mildly wary of how 
>> correct it might be overall.
>>
>> (Also now I'm wondering why I didn't just use dev_fwnode() there...)
> 
> 
> Yes making that change in the tegra-smmu driver does fix it.

Ace, thanks for confirming! I was just writing a follow-up to say that 
I've pretty much convinced myself that this (proper diff below) should 
in fact be the right thing to do in general as well :)

Will, Joerg, would you prefer to have a standalone fix patch for the 
nvidia/tegra branch to then re-merge fwspec-ops-removal and fix up the 
conflict, or just a patch on top of fwspec-ops-removal as below?

Thanks,
Robin.

----->8-----
diff --git a/drivers/iommu/tegra-smmu.c b/drivers/iommu/tegra-smmu.c
index 4365d9936e68..7f633bb5efef 100644
--- a/drivers/iommu/tegra-smmu.c
+++ b/drivers/iommu/tegra-smmu.c
@@ -837,7 +837,7 @@ static int tegra_smmu_configure(struct tegra_smmu 
*smmu, struct device *dev,
  	const struct iommu_ops *ops = smmu->iommu.ops;
  	int err;

-	err = iommu_fwspec_init(dev, of_fwnode_handle(dev->of_node));
+	err = iommu_fwspec_init(dev, dev_fwnode(smmu->dev));
  	if (err < 0) {
  		dev_err(dev, "failed to initialize fwspec: %d\n", err);
  		return err;

  parent reply	other threads:[~2024-07-12 15:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 11:40 [PATCH v3 0/5] iommu: Remove iommu_fwspec ops Robin Murphy
2024-07-02 11:40 ` [PATCH v3 1/5] iommu/mediatek-v1: Clean up redundant fwspec checks Robin Murphy
2024-07-02 11:40 ` [PATCH v3 2/5] iommu: Resolve fwspec ops automatically Robin Murphy
2024-07-12 11:01   ` Jon Hunter
2024-07-12 11:48     ` Robin Murphy
2024-07-12 15:24       ` Jon Hunter
2024-07-12 15:26         ` Will Deacon
2024-07-12 15:28         ` Robin Murphy [this message]
2024-07-12 15:31           ` Will Deacon
2024-07-12 15:34             ` Robin Murphy
2024-07-12 15:26       ` Will Deacon
2024-07-02 11:40 ` [PATCH v3 3/5] ACPI: Retire acpi_iommu_fwspec_ops() Robin Murphy
2024-07-02 11:40 ` [PATCH v3 4/5] OF: Simplify of_iommu_configure() Robin Murphy
2024-07-02 11:40 ` [PATCH v3 5/5] iommu: Remove iommu_fwspec ops Robin Murphy
2024-07-04 14:19 ` [PATCH v3 0/5] " Will Deacon

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=82624cf6-98ad-47df-8dcd-368117600805@arm.com \
    --to=robin.murphy@arm.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=guohanjun@huawei.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=sudeep.holla@arm.com \
    --cc=will@kernel.org \
    --cc=yong.wu@mediatek.com \
    /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