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=-6.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham 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 722D2C2D0EF for ; Tue, 31 Mar 2020 09:15:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 48C07208E0 for ; Tue, 31 Mar 2020 09:15:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1585646120; bh=WdrpLdSsYq3kQgncJPzNCgTZYn/K/kVhYZKhp/uifWk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=0sk8B1VgNcQmXvi6Lk5Bt0kX2/0e8sPjdpabGp+csFwI13EPMZE4d3IhcfRdKCG7C wBQKaC3tcGHkIQBfHiT+cljCbVfPHcN2PvJrmNOkqw5G+c35KLcC6omlVXTG0P5Cy4 9A4ugfzUxjNgsx/GSKD2wbFc0yIRZjZXJXxBxw+k= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730798AbgCaJPT (ORCPT ); Tue, 31 Mar 2020 05:15:19 -0400 Received: from mail.kernel.org ([198.145.29.99]:35370 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731468AbgCaJPO (ORCPT ); Tue, 31 Mar 2020 05:15:14 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1727620675; Tue, 31 Mar 2020 09:15:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1585646113; bh=WdrpLdSsYq3kQgncJPzNCgTZYn/K/kVhYZKhp/uifWk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=DVMBY41RnwjtWliTvTgIwKP3qeJQmzMFNYW8Cg2VNl3JShBZ74BeKzGagChifGIrT Sy5fZwlqEMwaDY/EMaYV9+Hc24KKx9w2f/p4FaJuDjDKN5nvxVAWBLjQIWWx/6THOq ivCCwr4b3A8jwVZ8oIWeKgCWK3hLnPI47qlLQv24= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Roger Quadros , stable@kernel.org, Tony Lindgren Subject: [PATCH 5.4 088/155] ARM: dts: dra7: Add bus_dma_limit for L3 bus Date: Tue, 31 Mar 2020 10:58:48 +0200 Message-Id: <20200331085428.103936610@linuxfoundation.org> X-Mailer: git-send-email 2.26.0 In-Reply-To: <20200331085418.274292403@linuxfoundation.org> References: <20200331085418.274292403@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Roger Quadros commit cfb5d65f25959f724081bae8445a0241db606af6 upstream. The L3 interconnect's memory map is from 0x0 to 0xffffffff. Out of this, System memory (SDRAM) can be accessed from 0x80000000 to 0xffffffff (2GB) DRA7 does support 4GB of SDRAM but upper 2GB can only be accessed by the MPU subsystem. Add the dma-ranges property to reflect the physical address limit of the L3 bus. Issues ere observed only with SATA on DRA7-EVM with 4GB RAM and CONFIG_ARM_LPAE enabled. This is because the controller supports 64-bit DMA and its driver sets the dma_mask to 64-bit thus resulting in DMA accesses beyond L3 limit of 2G. Setting the correct bus_dma_limit fixes the issue. Signed-off-by: Roger Quadros Cc: stable@kernel.org Signed-off-by: Tony Lindgren Signed-off-by: Greg Kroah-Hartman --- arch/arm/boot/dts/dra7.dtsi | 1 + 1 file changed, 1 insertion(+) --- a/arch/arm/boot/dts/dra7.dtsi +++ b/arch/arm/boot/dts/dra7.dtsi @@ -148,6 +148,7 @@ #address-cells = <1>; #size-cells = <1>; ranges = <0x0 0x0 0x0 0xc0000000>; + dma-ranges = <0x80000000 0x0 0x80000000 0x80000000>; ti,hwmods = "l3_main_1", "l3_main_2"; reg = <0x0 0x44000000 0x0 0x1000000>, <0x0 0x45000000 0x0 0x1000>;