Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp920258pxu; Sun, 25 Oct 2020 22:11:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxFi6utlZ9iXSr6MBn0zrVvhpBR0d/cxvzJnD4bmmnUrQPg/wsd5FzlcVlMdhJlcPv/s6j4 X-Received: by 2002:a17:906:a896:: with SMTP id ha22mr2028483ejb.440.1603689088518; Sun, 25 Oct 2020 22:11:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603689088; cv=none; d=google.com; s=arc-20160816; b=Uub0KQoPM+rL5xjzasXDFQ7k8DIOtVhWsBAH85dU+1dMVukolpIRVBDvRqdCvLjSqt 9nBpciazgH4cA9IrCS2OPOv/Vz8m1jJIjGn9Q91EVgNS9IPSorpTB99Q71LN5FVwiJEt WSoJLovnqWuk6QqLqNorSozHUTH2ops2n3XqH3lB4NF7K1z8H5TbxPK2nzRLH6k8E6Ti tiPInVQL3m8/1F0tFE+oLr71eKnh73hWCsQ/0Y9Wu5UslTWIjsv1TSp0/eAeRonVsw2h w5wBpezRvDo17V5ID5oKbtYuE9WwBCFDZBLnqkErLqlJNCplKIa8yDKdWmxLmqffHsMT 81Gg== 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=dXOEcubyn0vvm8s40OjapAeFa5+iITm9vJ6VmcdmZBE=; b=WqhOuAjUjhGUwiJ1aWMfCVCGk1RruRtpdQ5/4C7ZR2JNCF1sn1DJjI58tkwBCpaFJt tQILcTi2uNG4f6yz7zQaX5gVGK+7fIVhWDrH4CJs6S+erfxsAqRmSKkHZ2Vl/Gx/IuXv f/DT5P+q2A80Xo8PhEUQsvYnvjBnZesiG42oGlIuacKiJjiBJEuWScmzjNLRY4m3g2UL kr7oDeqMqOW41D/HNGwPpZmXx2ogJTtHs5CrfhBwSVhQpJlEnPAzYux2G02cX/pzlffH CEXlvtavmvvfQMZj3jiSwvWrYcWVAvOTe+8V6d2EBBncM8+nfK9jdZT0jzZuzcp1gfia VRdA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h25si6374611edt.103.2020.10.25.22.11.06; Sun, 25 Oct 2020 22:11:28 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1421383AbgJZCVO (ORCPT + 99 others); Sun, 25 Oct 2020 22:21:14 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:3004 "EHLO szxga06-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1421377AbgJZCVO (ORCPT ); Sun, 25 Oct 2020 22:21:14 -0400 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.59]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4CKJVN40gBzhb9K; Mon, 26 Oct 2020 10:21:16 +0800 (CST) Received: from [127.0.0.1] (10.174.178.230) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.487.0; Mon, 26 Oct 2020 10:21:09 +0800 Subject: Re: [PATCH v2 1/2] arm64: dts: broadcom: clear the warnings caused by empty dma-ranges To: Arnd Bergmann CC: Florian Fainelli , Rob Herring , Ray Jui , Scott Branden , bcm-kernel-feedback-list , Andy Gross , Bjorn Andersson , linux-arm-msm , devicetree , linux-arm-kernel , linux-kernel References: <20201016090833.1892-1-thunder.leizhen@huawei.com> <20201016090833.1892-2-thunder.leizhen@huawei.com> <0eee3fd2-7400-7de7-27a7-7fcaa0955854@gmail.com> From: "Leizhen (ThunderTown)" Message-ID: <07ab3bdd-dcb1-5a59-d813-f82451b3f028@huawei.com> Date: Mon, 26 Oct 2020 10:21:08 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.178.230] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/10/23 15:17, Arnd Bergmann wrote: > On Sun, Oct 18, 2020 at 4:10 AM Leizhen (ThunderTown) > wrote: >> On 2020/10/17 3:27, Florian Fainelli wrote: >>> On 10/16/20 11:23 AM, Arnd Bergmann wrote: >>>> On Fri, Oct 16, 2020 at 6:48 PM Florian Fainelli wrote: >>>>> On 10/16/20 4:01 AM, Arnd Bergmann wrote: >>>>>> On Fri, Oct 16, 2020 at 11:09 AM Zhen Lei wrote: >>>>>>> >>>>>>> Suggested-by: Arnd Bergmann >>>>>>> Signed-off-by: Zhen Lei >>>>>> >>>>>> Acked-by: Arnd Bergmann >>>>>> >>>>>> I see that at least the 'bcd' and 'xhci' devices in fact try to >>>>>> use 64-bit DMA. It would be good to test this on actual >>>>>> hardware to ensure that it works correctly when this is enabled. >>>>>> >>>>>> Ideally avoiding the swiotlb bounce buffering should only >>>>>> make it faster here, but there are many chips on which >>>>>> 64-bit DMA is broken in some form. >>>>> >>>>> Is this change really an improvement though? This 'usb' pseudo bus node >>>>> could just keep being defined with #address-cells = <1> and #size-cells >>>>> = <1> so as to satisfy the 'reg' definition however we could just adjust >>>>> dma-ranges to indicate full 64-bit addressing capability. Would not that >>>>> work? >>>> >>>> When #address-cells is '1', you cannot specify dma-ranges that >>>> go beyond a 32-bit address range. >>> >>> Would not it be enough to remove the 'dma-ranges' property though? Sorry >>> for being slow here. >> >> Remove the 'dma-ranges' property should also work. After all, it is equivalent >> to the original empty dma-ranges scheme. In addition, since the IOMMU nodes are >> defined, it should be enabled. > > Are you sure? I was expecting the IOMMU not to get used here since > the devices do contain list an 'iommus' property. OK,If the SMMU maybe disabled, then your proposal is necessary. > > Arnd > > . >