From: Steven Price <steven.price@arm.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Heiko Stuebner <heiko@sntech.de>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH] iommu/rockchip: Add missing set_platform_dma_ops callback
Date: Wed, 22 Mar 2023 16:04:25 +0000 [thread overview]
Message-ID: <bee3e168-3fc3-89e8-6b10-a830f052cf55@arm.com> (raw)
In-Reply-To: <ZBsb01emBJJMZIt0@ziepe.ca>
On 22/03/2023 15:16, Jason Gunthorpe wrote:
> On Wed, Mar 22, 2023 at 03:08:41PM +0000, Steven Price wrote:
>> @@ -1035,8 +1055,9 @@ static int rk_iommu_attach_device(struct iommu_domain *domain,
>> if (iommu->domain == domain)
>> return 0;
>>
>> - if (iommu->domain)
>> - rk_iommu_detach_device(iommu->domain, dev);
>> + ret = rk_iommu_identity_attach(&rk_identity_domain, dev);
>> + if (ret)
>> + return ret;
>
>>
>> iommu->domain = domain;
>>
>> @@ -1049,8 +1070,6 @@ static int rk_iommu_attach_device(struct iommu_domain *domain,
>> return 0;
>>
>> ret = rk_iommu_enable(iommu);
>> - if (ret)
>> - rk_iommu_detach_device(iommu->domain, dev);
>
> I think this still needs error handling, it should put it back to the
> identity domain and return an error code if it fails to attach to the
> requested domain.
What confused me here is that there's already a call to
rk_iommu_identity_attach() just above. But I can obviously add a...
if (ret)
rk_iommu_identity_attach(&rk_identity_domain, dev);
... in here. But I don't know how to handle an error from
rk_iommu_identity_attach() at this point. Does it need handling - is a
WARN_ON sufficient?
> It should also initlaize iommu->domain to the identity domain when the
> iommu struct is allocated. The iommu->domain should never be
> NULL. identity domain means the IOMMU is turned off which was
> previously called "detached".
I presume you mean in rk_iommu_probe()?
> Otherwise it looks like I would expect, thanks
Ok, I'll give it a spin with the above changes and post a v2 of this patch.
Thanks,
Steve
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2023-03-22 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 16:41 [PATCH] iommu/rockchip: Add missing set_platform_dma_ops callback Steven Price
2023-03-21 14:38 ` Jason Gunthorpe
2023-03-22 9:02 ` Steven Price
2023-03-22 12:50 ` Jason Gunthorpe
2023-03-22 15:08 ` Steven Price
2023-03-22 15:16 ` Jason Gunthorpe
2023-03-22 16:04 ` Steven Price [this message]
2023-03-22 17:36 ` Jason Gunthorpe
2023-03-24 11:17 ` Steven Price
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=bee3e168-3fc3-89e8-6b10-a830f052cf55@arm.com \
--to=steven.price@arm.com \
--cc=baolu.lu@linux.intel.com \
--cc=heiko@sntech.de \
--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-rockchip@lists.infradead.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