From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 93F5CC3A5A1 for ; Mon, 19 Aug 2019 18:19:47 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6EF6C22CEC for ; Mon, 19 Aug 2019 18:19:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="Bf0p30PB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6EF6C22CEC Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:To :From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=pxkTMzK0uYrl/9PLRIfQaM0RwWAgCcPk07R7dq0BKx8=; b=Bf0p30PBR17ZZB aiDR1s+eFuh6FosZQHrT+IbTHbrdyPmMxuFdxQ/+7idqFSnYDBXavgYwVVzKb3Ciiovnrm6JguE1U Ng0vznVhvlGLosgl7Py8tCkleTh4HFW7Ul43unkaA1loDHtMfdbJsvVDkF56BBGbixy8BNsJXmUVV PysTeYJJSp46JDrPwHQj3POfhOlnrXREg7M97NjGh8l1P63MsRc9ct+o1J4yZAJBqmGd24jrxietx 7TolNT27O2EZjgfy9rD/l1zk6M0VO6bMQRYKLI8GdqSH2PIre2qSZtLWVo/B1PvQwYbdS0rZ+9RSx FldRa82/RbfksOuFZd+Q==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hzmFp-0003cM-9G; Mon, 19 Aug 2019 18:19:41 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hzmFl-0003ah-B1 for linux-arm-kernel@lists.infradead.org; Mon, 19 Aug 2019 18:19:38 +0000 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 C0603360; Mon, 19 Aug 2019 11:19:35 -0700 (PDT) Received: from e110467-lin.cambridge.arm.com (e110467-lin.cambridge.arm.com [10.1.197.57]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id D565D3F246; Mon, 19 Aug 2019 11:19:34 -0700 (PDT) From: Robin Murphy To: will@kernel.org Subject: [PATCH 0/4] iommu/io-pgtable: Cleanup and prep for split tables Date: Mon, 19 Aug 2019 19:19:27 +0100 Message-Id: X-Mailer: git-send-email 2.21.0.dirty MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190819_111937_426269_174F7984 X-CRM114-Status: GOOD ( 10.86 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: robdclark@gmail.com, joro@8bytes.org, jcrouse@codeaurora.org, iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi all, Although the io-pgtable-arm formats started out with the notion of being able to provide a complete ready-to-use context for VMSA-compliant users to consume, the reality is that users inevitably still have to make their own adjustments to that context anyway. Worse, though, is that some of that cruft starts actively getting in the way of future work like supporting split tables using both TTBRs. These patches clean things up by stripping io-pgatble's context back to just the parts directly relevant to what it abstracts, and formalising the expectation that this only forms a basis from which users can construct their own complete context. Series based on v2 of "Arm SMMU refactoring" here: https://patchwork.kernel.org/patch/11096263/ Robin. Robin Murphy (4): iommu/io-pgtable-arm: Rationalise MAIR handling iommu/io-pgtable-arm: Rationalise TTBRn handling iommu/io-pgtable-arm: Rationalise TCR handling iommu/io-pgtable-arm: Prepare for TTBR1 usage drivers/iommu/arm-smmu-v3.c | 11 +++-------- drivers/iommu/arm-smmu.c | 14 +++++++------- drivers/iommu/arm-smmu.h | 2 ++ drivers/iommu/io-pgtable-arm-v7s.c | 22 +++++++++------------- drivers/iommu/io-pgtable-arm.c | 23 +++++++++-------------- drivers/iommu/ipmmu-vmsa.c | 4 ++-- drivers/iommu/msm_iommu.c | 4 ++-- drivers/iommu/mtk_iommu.c | 4 ++-- drivers/iommu/qcom_iommu.c | 9 ++++----- include/linux/io-pgtable.h | 6 +++--- 10 files changed, 43 insertions(+), 56 deletions(-) -- 2.21.0.dirty _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel