Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp598943pxb; Wed, 27 Jan 2021 16:17:59 -0800 (PST) X-Google-Smtp-Source: ABdhPJwd7RcOqultFG6CITxgJqAoZq2Z2UfXZywX7viIlSuZ3F563PAaZBmWJ8oZ30CEZOKqj2GU X-Received: by 2002:a17:906:d159:: with SMTP id br25mr8591880ejb.398.1611793079029; Wed, 27 Jan 2021 16:17:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611793079; cv=none; d=google.com; s=arc-20160816; b=OXDznZju5jpo50uEBrm+semin3K0jllr5f0s4PwlPeqGsl2ePQKkP1+rs6rVVvfZQ/ i2A4AG0IjBxSItEkQ78VhP4PZgHDGUlqYPwKHvKPIleiJRe/8HmuA9IPIpWFEEPo2Z16 6/Ch2AZlj0xlaTWSorcRvnkTbr0bgCnYKHczt4ESGG27+d3XZxm0HDyuwO3Gjw65hqMb dq2FVv+NHRBp93SoRC5aJQ75zulrLerac6ZMdplxgxyeRqPr8IIcTFKRc8PmgHbf+uke PnMUJrItFC6f0C8yL2nJHkWwVF13vnIXIK1eUa2E5VRYXL1Ok3wHuK69LUfl2lJdcHfB Y32A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=dZxIK2U1f/0coW4ng6dAkKHyPVnVwtuSud1qAu4nTR4=; b=gGMqCaQ6iKAVqHnpjMjzBxxw9yBlnzqV6brszrysigHF1S3OZ9Xm9HcKnldMaT16zv IBoWCoYKNS0dOB/ALfYwSt0fkhapDT+/0Fe0U61eugKjqSrk6QOLprQhI0XXPgGkylRs Ryad+IRJU2eQZhNvkWZjTNFqMbKuyGIsIwnlQ8fJDII4Ma5c1pG693G540wqSBUPqXub o3hR9RTd5GeS9lQJ8sxh0de83FGm8kQOURSLlcMkGVB+6yYUUHG9uApBEdEJai7e6/Ha A2Qc3rG7R1GpCXH9fNz3lqleOhu3SxIT6Zn1x/8esqKcvEocCmuF43rwhhuPF5ZKGz1z vmQg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q18si1455051ejt.469.2021.01.27.16.17.35; Wed, 27 Jan 2021 16:17:59 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344483AbhA0Tjq (ORCPT + 99 others); Wed, 27 Jan 2021 14:39:46 -0500 Received: from foss.arm.com ([217.140.110.172]:34058 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344566AbhA0ThV (ORCPT ); Wed, 27 Jan 2021 14:37:21 -0500 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 95AF5106F; Wed, 27 Jan 2021 11:36:34 -0800 (PST) Received: from [10.57.47.135] (unknown [10.57.47.135]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C789B3F68F; Wed, 27 Jan 2021 11:36:31 -0800 (PST) Subject: Re: [PATCH v2] of/device: Update dma_range_map only when dev has valid dma-ranges To: Rob Herring Cc: Frank Rowand , Christoph Hellwig , Marek Szyprowski , Joerg Roedel , Matthias Brugger , Will Deacon , Krzysztof Kozlowski , Tomasz Figa , "moderated list:ARM/Mediatek SoC support" , srv_heupstream , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , linux-arm-kernel , Linux IOMMU , Nicolas Boichat , Yong Wu , Paul Kocialkowski References: <20210119105203.15530-1-yong.wu@mediatek.com> <159d4486-bb7e-249d-2bad-f5bba839041d@arm.com> From: Robin Murphy Message-ID: <8f742f94-4087-7fb6-4b7c-9058593b67cf@arm.com> Date: Wed, 27 Jan 2021 19:36:30 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: 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 2021-01-27 19:09, Rob Herring wrote: > On Wed, Jan 27, 2021 at 7:13 AM Robin Murphy wrote: >> >> [ + Christoph, Marek ] >> >> On 2021-01-27 13:00, Paul Kocialkowski wrote: >>> Hi, >>> >>> On Tue 19 Jan 21, 18:52, Yong Wu wrote: >>>> The commit e0d072782c73 ("dma-mapping: introduce DMA range map, >>>> supplanting dma_pfn_offset") always update dma_range_map even though it was >>>> already set, like in the sunxi_mbus driver. the issue is reported at [1]. >>>> This patch avoid this(Updating it only when dev has valid dma-ranges). >>>> >>>> Meanwhile, dma_range_map contains the devices' dma_ranges information, >>>> This patch moves dma_range_map before of_iommu_configure. The iommu >>>> driver may need to know the dma_address requirements of its iommu >>>> consumer devices. >>> >>> Just a gentle ping on this issue, it would be nice to have this fix merged >>> ASAP, in the next RC :) >> >> Ack to that - Rob, Frank, do you want to take this through the OF tree, >> or shall we take it through the DMA-mapping tree like the original culprit? > > I've already got some fixes queued up and can take it. Brilliant, thanks! > Suggested-by doesn't mean you are happy with the implementation. So > Acked-by or Reviewed-by? It still feels slightly awkward to give a tag to say "yes, this is exactly what I suggested", but for the avoidance of doubt, Reviewed-by: Robin Murphy Cheers, Robin.