Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp818190ybl; Thu, 22 Aug 2019 05:28:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqyV0PT/YdexZPGZt/sMIvjqB8cTMI77sVW8M/GOifjFtzKd/9pFeulolzOCNb1DcU2Pk0PC X-Received: by 2002:a17:902:33a5:: with SMTP id b34mr6745950plc.286.1566476902015; Thu, 22 Aug 2019 05:28:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566476902; cv=none; d=google.com; s=arc-20160816; b=vv8Y5O+3okun1O69MQocbVUffUHZEcxROI8d8/ahE8YO+rABPBEvRcwkhYFdSQylbk mGy8MbLPyF6ClPEpZOtOwMs6TjVHCU/2hluG8IiS7BBgjLOBkP35dEFVgTK5HVgkcvD/ VAmF9HM/w2Vpj0EHcr+VgQbq49Yux8V/KDO5EWdSAy1E9Hua+Eja91/Kcuop2nnIKBOW NruQd+S7QtdtsgMXL+nQQthEld32UAOgOQHwbnr7VHF62cQX0tf6TbN1IkKmsWHNSV+C JuWN97jn15NyJV6Tx1ktovABuBTUm8XVD7DO/FnANn+iRAAGaF+BJe94kE4UPbNlytV0 cIww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=ArMbOL1Khv2xcXrffuAm4Z73XQcWUc/pYej/Khz+Xbo=; b=Lrn6YY1XbmBCw1iw/9fCEZ9o32xtEQ2N2bvw4nXiS7KW+nKtr+Zyj4dpQP5FJmZ3bL FSkQu0JuXvZSTFhYjOr1B+6dEFjm13J6x5ga4rKmV7qkiEyXM+gRtUm+qpzT/wZbzhQ8 Vzqap4mW9KDz8hWffrqlrQjLm+jeJ3caG8R7ldgax6e6qG+zmho71zWiWBYSZAPKj63D YD/mvZp4sbpxJyWPGUShALukXFQKaPA1E6GsFp0c2uqck3+xup5PHauELRWX6k60uBWp 0CoReAhR94s0xIxLkR0bY3cVN39OnAa9AV64JJvf8u5k2f0o/udm28Yfd2CzsznxCYH8 j08A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b18si17253256pls.125.2019.08.22.05.28.06; Thu, 22 Aug 2019 05:28:21 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733259AbfHVKJJ (ORCPT + 99 others); Thu, 22 Aug 2019 06:09:09 -0400 Received: from foss.arm.com ([217.140.110.172]:42950 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731583AbfHVKJH (ORCPT ); Thu, 22 Aug 2019 06:09:07 -0400 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 3587F15A2; Thu, 22 Aug 2019 03:09:07 -0700 (PDT) Received: from [192.168.1.123] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id E13E43F246; Thu, 22 Aug 2019 03:09:02 -0700 (PDT) Subject: Re: [PATCH v10 09/23] iommu/io-pgtable-arm-v7s: Extend to support PA[33:32] for MediaTek To: Yong Wu , Will Deacon Cc: youlin.pei@mediatek.com, devicetree@vger.kernel.org, Nicolas Boichat , cui.zhang@mediatek.com, srv_heupstream@mediatek.com, chao.hao@mediatek.com, Joerg Roedel , linux-kernel@vger.kernel.org, Evan Green , Tomasz Figa , iommu@lists.linux-foundation.org, Rob Herring , linux-mediatek@lists.infradead.org, Matthias Brugger , ming-fan.chen@mediatek.com, anan.sun@mediatek.com, Matthias Kaehlcke , linux-arm-kernel@lists.infradead.org References: <1566395606-7975-1-git-send-email-yong.wu@mediatek.com> <1566395606-7975-10-git-send-email-yong.wu@mediatek.com> <20190821152448.qmoqjh5zznfpdi6n@willie-the-truck> <1566464186.11621.7.camel@mhfsdcap03> From: Robin Murphy Message-ID: <10d5122d-3375-161b-9356-2ddfc1c835bd@arm.com> Date: Thu, 22 Aug 2019 11:08:58 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <1566464186.11621.7.camel@mhfsdcap03> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-08-22 9:56 am, Yong Wu wrote: > On Wed, 2019-08-21 at 16:24 +0100, Will Deacon wrote: >> On Wed, Aug 21, 2019 at 09:53:12PM +0800, Yong Wu wrote: >>> MediaTek extend the arm v7s descriptor to support up to 34 bits PA where >>> the bit32 and bit33 are encoded in the bit9 and bit4 of the PTE >>> respectively. Meanwhile the iova still is 32bits. >>> >>> Regarding whether the pagetable address could be over 4GB, the mt8183 >>> support it while the previous mt8173 don't, thus keep it as is. >>> >>> Signed-off-by: Yong Wu >>> --- >>> drivers/iommu/io-pgtable-arm-v7s.c | 32 +++++++++++++++++++++++++------- >>> include/linux/io-pgtable.h | 7 +++---- >>> 2 files changed, 28 insertions(+), 11 deletions(-) >> >> [...] >> >>> @@ -731,7 +747,9 @@ static struct io_pgtable *arm_v7s_alloc_pgtable(struct io_pgtable_cfg *cfg, >>> { >>> struct arm_v7s_io_pgtable *data; >>> >>> - if (cfg->ias > ARM_V7S_ADDR_BITS || cfg->oas > ARM_V7S_ADDR_BITS) >>> + if (cfg->ias > ARM_V7S_ADDR_BITS || >>> + (cfg->oas > ARM_V7S_ADDR_BITS && >>> + !(cfg->quirks & IO_PGTABLE_QUIRK_ARM_MTK_EXT))) >> >> Please can you instead change arm_v7s_alloc_pgtable() so that it allows an >> ias of up to 34 when the IO_PGTABLE_QUIRK_ARM_MTK_EXT is set? > > Here I only simply skip the oas checking for our case. then which way do > your prefer? something like you commented before:? > > > if (cfg->ias > ARM_V7S_ADDR_BITS) > return NULL; > > if (cfg->quirks & IO_PGTABLE_QUIRK_ARM_MTK_EXT) { > if (!IS_ENABLED(CONFIG_PHYS_ADDR_T_64BIT)) > cfg->oas = min(cfg->oas, ARM_V7S_ADDR_BITS); > else if (cfg->oas > 34) > return NULL; > } else if (cfg->oas > ARM_V7S_ADDR_BITS) { > return NULL; > } All it should take is something like: if (cfg->quirks & IO_PGTABLE_QUIRK_ARM_MTK_EXT) max_oas = 34; else max_oas = 32; if (cfg->oas > max_oas) return NULL; or even just: if (cfg->oas > 32 || (cfg->quirks & IO_PGTABLE_QUIRK_ARM_MTK_EXT && cfg->oas > 34)) return NULL; (and if we prefer the latter style, perhaps we could introduce some kind of "is_mtk_4gb()" helper to save on verbosity) We shouldn't need to care about the size of phys_addr_t either way - the fact is that the MTK format can still encode up to 34 bits of PA regardless of whether callers can actually pass addresses that large. Robin.