Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp818437ybh; Tue, 10 Mar 2020 08:49:02 -0700 (PDT) X-Google-Smtp-Source: ADFU+vs4qFNtf8XS/h1CHCdvlmy73xVWJuZIqeggqOdnYoaEwO3YnG2c/fyvUBnim81rSZjjRzuc X-Received: by 2002:aca:4bc5:: with SMTP id y188mr1662210oia.9.1583855342042; Tue, 10 Mar 2020 08:49:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583855342; cv=none; d=google.com; s=arc-20160816; b=ucg19pVVI7qFfkn6SD01y2IQMn8iJOnJAFoqGVnTvcK5SY4Q3MBOjScyV+EL1YJXbT 7QnaloMfYt6INFPgcQ7dAiS2ddCs9JCUc/+kcRxlPzPlQqzQj7VbbwoUoSoQNlIp9N03 pKf46/zRKnPU9J5eglNsRryec1verCV5FhBPepS29gMZtNtDuw+mF2pbZzx025SBZWOq nv+K4kkzsSY/SKbhvT7ayYuVCm9mE/bO5s0IeWa4CqSkL6nyEgaDwaKAHNMHOEl32ARf BTYyVkYk/qx0TiORd9ppeipMzAv09XgnvuCx6czZG+iorrlarPL4nq42s3+WbyfpzWCj M78Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=9QEwfFKKLzUTSs81Xm6Ab06WnUA/QksUJRGFnc68e5M=; b=zdJOIozJoPrhmjtB7atCWoKurZWmqoDTxUwiD/sTb7GgV5bzYc+3sP1DrsQHJx/xf8 kPQ14kpHeQJS58QOaGOkvyjCDhz3/W4vI+OXxw0G3XlaMBaVQDAwkxEYGk6Yl+g0I0rT ZV5GpzCZ1/iyqeqpj18+iMvkzyqP9xHOtrjrNGLl+98Uo6ACLLcnaTFKbs0Mukcv2UAe PDG4/RLVomUI6iNngKFKibmvIqWhsyvm3XIoi/glh3X6X8aDzqLg4HLIeBPg9zyRUIAo RLZGv84fe2xa+j+S4QIP1HtmEgIE5+m5unTOdnKh6K87yeX3b/ZnuLF0MkRzatCLg6Du fH+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u135si2076381oif.248.2020.03.10.08.48.49; Tue, 10 Mar 2020 08:49:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726604AbgCJPsd (ORCPT + 99 others); Tue, 10 Mar 2020 11:48:33 -0400 Received: from muru.com ([72.249.23.125]:59512 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726477AbgCJPsd (ORCPT ); Tue, 10 Mar 2020 11:48:33 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 64DAF810A; Tue, 10 Mar 2020 15:49:18 +0000 (UTC) Date: Tue, 10 Mar 2020 08:48:29 -0700 From: Tony Lindgren To: Tero Kristo Cc: Roger Quadros , hch@lst.de, robin.murphy@arm.com, robh+dt@kernel.org, nm@ti.com, nsekhar@ti.com, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ARM: dts: dra7: Add bus_dma_limit for L3 bus Message-ID: <20200310154829.GS37466@atomide.com> References: <20200310115309.31354-1-rogerq@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Tero Kristo [200310 14:46]: > On 10/03/2020 13:53, Roger Quadros wrote: > > The L3 interconnect can access only 32-bits of address. > > Add the dma-ranges property to reflect this limit. > > > > This will ensure that no device under L3 is > > given > 32-bit address for DMA. > > > > Issue was observed only with SATA on DRA7-EVM with 4GB RAM > > and CONFIG_ARM_LPAE enabled. This is because the controller > > can perform 64-bit DMA and was setting the dma_mask to 64-bit. > > > > Setting the correct bus_dma_limit fixes the issue. > > This seems kind of messy to modify almost every DT node because of this.... > Are you sure this is the only way to get it done? No way to modify the sata > node only which is impacted somehow? > > Also, what if you just pass 0xffffffff to the dma-ranges property? That > would avoid modifying every node I guess. Also, I think these interconnects are not limited to 32-bit access. So yeah I too would prefer a top level dma-ranges property assuming that works. I guess there dma-ranges should not be 0xffffffff though if limited to 2GB :) Regards, Tony