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=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 C7482C2D0E2 for ; Thu, 24 Sep 2020 09:36:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 76FA0206C9 for ; Thu, 24 Sep 2020 09:36:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727089AbgIXJgw (ORCPT ); Thu, 24 Sep 2020 05:36:52 -0400 Received: from foss.arm.com ([217.140.110.172]:40048 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726614AbgIXJgw (ORCPT ); Thu, 24 Sep 2020 05:36:52 -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 9AFC911D4; Thu, 24 Sep 2020 02:36:51 -0700 (PDT) Received: from [10.57.48.76] (unknown [10.57.48.76]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 0343E3F73B; Thu, 24 Sep 2020 02:36:48 -0700 (PDT) Subject: Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables To: Joerg Roedel Cc: Poonam Aggrwal , robh@kernel.org, Joerg Roedel , Arnd Bergmann , Richard Weinberger , Naresh Kamboju , open list , lkft-triage@lists.linaro.org, "open list:IOMMU DRIVERS" , Linux-Next Mailing List , linux-mtd@lists.infradead.org, Miquel Raynal , Suram Suram , masonccyang@mxic.com.tw, Will Deacon , Zhiqiang.Hou@nxp.com References: <20200924090349.GF27174@8bytes.org> <20200924092546.GJ27174@8bytes.org> From: Robin Murphy Message-ID: Date: Thu, 24 Sep 2020 10:36:47 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: <20200924092546.GJ27174@8bytes.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-09-24 10:25, Joerg Roedel wrote: > Hi Robin, > > On Thu, Sep 24, 2020 at 10:08:46AM +0100, Robin Murphy wrote: >> This should be fixed by https://lore.kernel.org/linux-iommu/daedc9364a19dc07487e4d07b8768b1e5934abd4.1600700881.git.robin.murphy@arm.com/T/#u >> (already in linux-next). > > Thanks! The question remains why this goes through the dma-mapping tree, > was it caused by a patch there? Yes, the issue was introduced by one of the changes in "dma-mapping: introduce DMA range map, supplanting dma_pfn_offset", so it only existed in the dma-mapping/for-next branch anyway. Robin.