Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp504467imw; Fri, 8 Jul 2022 06:51:11 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uDUh/jUcaB8waRExB/hLqBzpBjRPw+7MQJnTKO89ionIZ1KRWwRp7tQorgzKc89/Uw25V1 X-Received: by 2002:a17:907:a427:b0:71b:6f0b:8beb with SMTP id sg39-20020a170907a42700b0071b6f0b8bebmr3630594ejc.496.1657288271375; Fri, 08 Jul 2022 06:51:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657288271; cv=none; d=google.com; s=arc-20160816; b=Ge2sw7Gpx9tPdTKkjkkHDKwE8VMkzSX5BpWFwxas9YX2mZv2CazfIKIoeex7kALTPz v451w1QRf9LLn8+jMM3JB4JB4C9jYSImxH1GLlqoNgoUyavmHGakjaCLXVImw2hF+0ik tLEcLp4Lmg29Sgp4tHF+lBNgJ7TuQ9uacP9Y3Tq4/khyiEfSM3s+iTOrknPt+t/kv+lq raXeXXB5z4i9f+6ioBXWtL1GR2KdmU029VeBqcX2X54MULRLjDyDmTSZQkeW3NxIJiqK d1e7vCf8jYlqVejtCi4KDtFepPu1270N/goUXkcsieYEo/+69RYIKCA6aDR2KryfNMUA fTuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=1Yam3y0DcCFqvtPSG9KOweCqxMOCqoZ/tVs5qs0X19I=; b=RJ/yV/Jp0Z1UeHLcHesDra4/qJYHEN8MkZESKVvsXf/cLWl+TbPegUB3iBIdcxw6dA Xd/oqmWVOSY5DJ5osSCqTf12F333M7foRvdLuP/8DsMRrrVxix+Yd9QiOMbuCDUcZm2y /G6r4IY71tcB0pT8BfmEyEkR+RsKD33TKwveBIf+RyMcRf/pxKZvhJGK6nK/JjNGOPiS wTyrC2OJFHUOSFbWYVkcNa2vyah6zHd9vaGg5ZisYUskwSd6ef1Wzog9asmx1l8ePbl3 1QHSCgfnggBfSt/gq+N0BbwewqPbhOsrx8TInpbNsaDUcU01DwjDnyMSH0LCah2gR8Qd 3Ozg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=kQj86bjG; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hq8-20020a1709073f0800b0071d3b6e50fbsi5033721ejc.402.2022.07.08.06.50.45; Fri, 08 Jul 2022 06:51:11 -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; dkim=pass header.i=@linaro.org header.s=google header.b=kQj86bjG; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237833AbiGHNSs (ORCPT + 99 others); Fri, 8 Jul 2022 09:18:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56812 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231287AbiGHNSr (ORCPT ); Fri, 8 Jul 2022 09:18:47 -0400 Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D46C71C91A for ; Fri, 8 Jul 2022 06:18:45 -0700 (PDT) Received: by mail-lj1-x236.google.com with SMTP id s14so25938624ljs.3 for ; Fri, 08 Jul 2022 06:18:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1Yam3y0DcCFqvtPSG9KOweCqxMOCqoZ/tVs5qs0X19I=; b=kQj86bjG5zvMHEWhoxQWhFXTOUb15TA7YqDTqLA361xfX3dMGb3sA66mMwl6cGu1Cp 6Q867H9s0YhApBd6xEXsnrThqvBSoz4fZBP7GLTRSaQ2QnK2HHIHWLF7Bkz+/ibQrGx9 WmOhWen94YFgjXDgtkMpIKy7LhOV3xpqHo7pF7uXoOeJux9kYLux8b8Da6NFvugnft3J 7IDixkpvl3CYYIAi1v+2agBHTgmcIGWQ7LyOylWYDH605GAIKDf+ueY84GGCLvQA03zg h7ZrE3ctcGYV6khkrm9AlNVaQcIRWiW0Aabx9L/vnPGrhtaV+DOamJDJZOY0RVy/mPqT Q1rA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1Yam3y0DcCFqvtPSG9KOweCqxMOCqoZ/tVs5qs0X19I=; b=qUnDNWt3Pe+ACJRKf7JXJsVxHUkB8KfgWTP6XvpBlE7KehsT+wCndke0jWqfJn6ZkP hqJlLl5Y19E5IULEIaIvbbACslOmu659fxCm9fXoK/dIbCzaXjfUN5Ds2W3k9Nx2PG+d I/mqXmPmvO3EaJeyhaWgPaH0MEZQQvR1Uek6PYZUV7a9PLczm8WnhjSK1J1vSQ02InmG CVeV8Sv9OCglgpmI58BGWa5dcMsMtn07W6BeIBbFFaCnBxfx0W7dzFEHTn24Sfa8VUlT HyQkWNJw4aCyfJIrl7ElNlgfP1mB2a34expwzSjjGZ+l3LxHcAtRZEIdgNXBZJaxGxx7 ofBQ== X-Gm-Message-State: AJIora/fFnV5aSTo/HCvptGTlKtUwgmmX+YQz6rKthGYXfJjwHmTPdb3 yHZs2xeXO3oba2m1hKlUx/9OhMaTx8/oAMR/5z4vLQ== X-Received: by 2002:a2e:a413:0:b0:25d:4844:9d65 with SMTP id p19-20020a2ea413000000b0025d48449d65mr1997343ljn.169.1657286324182; Fri, 08 Jul 2022 06:18:44 -0700 (PDT) MIME-Version: 1.0 References: <20220702213724.3949-1-semen.protsenko@linaro.org> <20220702213724.3949-2-semen.protsenko@linaro.org> <9afb1e98-706f-ed61-892c-e3cc321364b4@linaro.org> In-Reply-To: <9afb1e98-706f-ed61-892c-e3cc321364b4@linaro.org> From: Sam Protsenko Date: Fri, 8 Jul 2022 16:18:32 +0300 Message-ID: Subject: Re: [PATCH 1/4] iommu/exynos: Set correct dma mask for SysMMU v5+ To: Krzysztof Kozlowski Cc: Marek Szyprowski , Joerg Roedel , Will Deacon , Robin Murphy , Janghyuck Kim , Cho KyongHo , Daniel Mentz , Sumit Semwal , iommu@lists.linux-foundation.org, iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham 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 Sun, 3 Jul 2022 at 21:50, Krzysztof Kozlowski wrote: > > On 02/07/2022 23:37, Sam Protsenko wrote: > > SysMMU v5+ supports 36 bit physical address space. Set corresponding DMA > > mask to avoid falling back to SWTLBIO usage in dma_map_single() because > > of failed dma_capable() check. > > > > The original code for this fix was suggested by Marek. > > > > Originally-by: Marek Szyprowski > > This is some tip specific tag, I don't think checkpatch allows it. > Either use suggesgted-by or co-developed-by + SoB. > Yes, checkpatch is swearing at that line, though I encountered that tag mentioning somewhere in Documentation. Will rework it in v2. > > Signed-off-by: Sam Protsenko > > --- > > drivers/iommu/exynos-iommu.c | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > > > diff --git a/drivers/iommu/exynos-iommu.c b/drivers/iommu/exynos-iommu.c > > index 71f2018e23fe..28f8c8d93aa3 100644 > > --- a/drivers/iommu/exynos-iommu.c > > +++ b/drivers/iommu/exynos-iommu.c > > @@ -647,6 +647,14 @@ static int exynos_sysmmu_probe(struct platform_device *pdev) > > } > > } > > > > + if (MMU_MAJ_VER(data->version) >= 5) { > > + ret = dma_set_mask(dev, DMA_BIT_MASK(36)); > > + if (ret) { > > + dev_err(dev, "Unable to set DMA mask: %d\n", ret); > > Missing cleanup: iommu_device_unregister > and probably also: iommu_device_sysfs_remove > Right. Also the correct cleanup should be added for failing iommu_device_register() case, above of the quoted code. Will do that in v2, thanks. Another thing is that "remove" method is missing. But guess I'll get to it later, when adding modularization support for this driver. > > + return ret; > > + } > > + } > > + > > /* > > * use the first registered sysmmu device for performing > > * dma mapping operations on iommu page tables (cpu cache flush) > > > Best regards, > Krzysztof