Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1114812rwl; Fri, 24 Mar 2023 06:32:29 -0700 (PDT) X-Google-Smtp-Source: AK7set/HTDavaQ/N43F08w9hvyhwC6m19rer6M1G3aUbJRdy6ppJQZJThGTjejvEC7f5a7I2o/0J X-Received: by 2002:a05:6a20:4ca5:b0:d9:162d:98e4 with SMTP id fq37-20020a056a204ca500b000d9162d98e4mr2375882pzb.54.1679664749337; Fri, 24 Mar 2023 06:32:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679664749; cv=none; d=google.com; s=arc-20160816; b=OKuyAW9SgH0xMwyQbha/+0bXTtGHndYkjlBH0UjKEdVAn5m6Cd12nzDT2w/xTvW7s8 7HXAVhgZXJ93vrZqsmXFAp5TU+wLZhLtIeI9lbbPMzgUsig0nIxisvPrcaWy77CkjndS GDBFneXJzcUjFuDRy6qR0fBOH7yqfVGvPiCmNyHD23zin6UtZtjgarHVxnMIkGHl7bb/ JayCBYRx8KBHHTi7F6Ur/3Coy1JaY2BqRzTaDCM4faSB2SCqklZsFEWVU3mFL2W5T13d W4bMu/vMQ6/GBzH9hfc+aRb/+HvVKE1DnOKg7lUY4miE7bOrQMjZJ+BLbBc1md+UT6LG ZkHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=sWwMZTIh1A8q4EA2bBGOJfN3dabaX/fmSAp4imtG//Q=; b=gFIWGu9suvwjthvCo9hS/e3Hws9aQKYC7P2LknmsmdU964lYI1vPFd96iMKmWLLgcG oFJ9bo6zI1sP0NFAZsJJPuXS5Z68OYKP80/AppQTl8IfOszEHvGPTXf1+j90dxv1QSkP ot7+Z+cyvaCTsocdBV0bpLOJhdmloEEMVrKK9rk6X/Yx5TtKVCR5cK1QxB5idVWgtYyc iIXG2nHceUNJMv/Xxhko8vRAou0LuLoPWLd+cUbdXPjMpc9FWwVD8Uqh7/pV6Xk0fa2X EiCbv5tkeY8j8i0FPQhvJxp6U64EPiLvBaATKOCi/k1rN8XWCug88MfKVpqDBBqMggKJ OR2w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s17-20020a632151000000b0050bee8d3e4bsi20782025pgm.691.2023.03.24.06.32.17; Fri, 24 Mar 2023 06:32:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231311AbjCXNYz (ORCPT + 99 others); Fri, 24 Mar 2023 09:24:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232064AbjCXNYx (ORCPT ); Fri, 24 Mar 2023 09:24:53 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id EB798EB4D for ; Fri, 24 Mar 2023 06:24:51 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B5A6111FB; Fri, 24 Mar 2023 06:25:35 -0700 (PDT) Received: from [10.1.28.32] (e122027.cambridge.arm.com [10.1.28.32]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 742EC3F766; Fri, 24 Mar 2023 06:24:49 -0700 (PDT) Message-ID: <859ef16c-bf31-78f2-f3df-cf0ff9493b3c@arm.com> Date: Fri, 24 Mar 2023 13:24:47 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v2] iommu/rockchip: Add missing set_platform_dma_ops callback Content-Language: en-GB To: Baolu Lu , Heiko Stuebner , Joerg Roedel , Jason Gunthorpe Cc: Will Deacon , Robin Murphy , iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org References: <20230324111127.221640-1-steven.price@arm.com> <8fda817c-98e7-1988-325d-52d09f3e61a8@linux.intel.com> From: Steven Price In-Reply-To: <8fda817c-98e7-1988-325d-52d09f3e61a8@linux.intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.3 required=5.0 tests=NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24/03/2023 13:16, Baolu Lu wrote: > On 2023/3/24 19:11, Steven Price wrote: >> Similar to exynos, we need a set_platform_dma_ops() callback for proper >> operation on ARM 32 bit after recent changes in the IOMMU framework >> (detach ops removal). But also the use of a NULL domain is confusing. >> >> Rework the code to have a singleton rk_identity_domain which is assigned >> to domain when using an identity mapping rather than "detaching". This >> makes the code easier to reason about. >> >> Signed-off-by: Steven Price >> --- >> Changes since v1[1]: >> >>   * Reworked the code to avoid a NULL domain, instead a singleton >>     rk_identity_domain is used instead. The 'detach' language is no >>     longer used. >> >> [1] >> https://lore.kernel.org/r/20230315164152.333251-1-steven.price%40arm.com >> >>   drivers/iommu/rockchip-iommu.c | 50 ++++++++++++++++++++++++++-------- >>   1 file changed, 39 insertions(+), 11 deletions(-) >> >> diff --git a/drivers/iommu/rockchip-iommu.c >> b/drivers/iommu/rockchip-iommu.c >> index f30db22ea5d7..437541004994 100644 >> --- a/drivers/iommu/rockchip-iommu.c >> +++ b/drivers/iommu/rockchip-iommu.c >> @@ -124,6 +124,7 @@ struct rk_iommudata { >>     static struct device *dma_dev; >>   static const struct rk_iommu_ops *rk_ops; >> +static struct iommu_domain rk_identity_domain; >>     static inline void rk_table_flush(struct rk_iommu_domain *dom, >> dma_addr_t dma, >>                     unsigned int count) >> @@ -980,26 +981,27 @@ static int rk_iommu_enable(struct rk_iommu *iommu) >>       return ret; >>   } >>   -static void rk_iommu_detach_device(struct iommu_domain *domain, >> -                   struct device *dev) >> +static int rk_iommu_identity_attach(struct iommu_domain >> *identity_domain, >> +                    struct device *dev) >>   { >>       struct rk_iommu *iommu; >> -    struct rk_iommu_domain *rk_domain = to_rk_domain(domain); >> +    struct rk_iommu_domain *rk_domain; >>       unsigned long flags; >>       int ret; >>         /* Allow 'virtual devices' (eg drm) to detach from domain */ >>       iommu = rk_iommu_from_dev(dev); >>       if (!iommu) >> -        return; >> +        return -ENODEV; >> + >> +    rk_domain = to_rk_domain(iommu->domain); >>         dev_dbg(dev, "Detaching from iommu domain\n"); >>   -    /* iommu already detached */ >> -    if (iommu->domain != domain) >> -        return; >> +    if (iommu->domain == identity_domain) >> +        return 0; >>   -    iommu->domain = NULL; >> +    iommu->domain = identity_domain; > > Where did identity_domain come from? Is it rk_identity_domain? It's a parameter of the function. In the case of the call in rk_iommu_attach_device() then, yes, it's rk_identity_domain. But this function is also the "attach_dev" callback of "rk_identity_ops". I'll admit this is cargo-culted from Jason's example: https://lore.kernel.org/linux-iommu/ZBnef7g7GCxogPNz@ziepe.ca/ Steve > Best regards, > baolu