[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2186418-d4d6-e1f4-5eb4-3bfafb5cebb2@arm.com>
Date: Thu, 24 Sep 2020 10:36:47 +0100
From: Robin Murphy <robin.murphy@....com>
To: Joerg Roedel <joro@...tes.org>
Cc: Poonam Aggrwal <poonam.aggrwal@....com>, robh@...nel.org,
Joerg Roedel <jroedel@...e.de>, Arnd Bergmann <arnd@...db.de>,
Richard Weinberger <richard@....at>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
linux-mtd@...ts.infradead.org,
Miquel Raynal <miquel.raynal@...tlin.com>,
Suram Suram <suram@....com>, masonccyang@...c.com.tw,
Will Deacon <will@...nel.org>, Zhiqiang.Hou@....com
Subject: Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU
page tables
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.
Powered by blists - more mailing lists