Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp9046401pxu; Mon, 28 Dec 2020 05:19:44 -0800 (PST) X-Google-Smtp-Source: ABdhPJzhMloPGcksHICjCXe3eOEULTe5qV7wLPEWLsnfw5kmDD9cfXEkBoSqmQizZ9UjOfpK3HNb X-Received: by 2002:a05:6402:a53:: with SMTP id bt19mr42966208edb.104.1609161584544; Mon, 28 Dec 2020 05:19:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609161584; cv=none; d=google.com; s=arc-20160816; b=kDLkQoHzcaoFgzRUBBDLHzDn+eaRC6Joqh4tTiBrM207QlXG/BYO+AYkt4p7HAO7wr One2oXZnCkuC09eePMJCjqC42v2ArZcK8h1I+1mLfZsAxRrKruhbeM4wwOSRJidRo815 00pU9i3f5pyuhc6YSCt0GZmLgViKCPZu7FsjErg6KPGUON7EmmeCl2tt7hj/jWm7aYP+ qLZ2KNj8KPhPd7szQGGl3uYGYq3G/kVGSbsxBbkZg8mB4JW+zax5wfOOvmtJhp/Qtpcf Fc3WdHqX/E0yZPvb2xCAqZztd22sWfO+cXCllKBf/UQhv7aG+mYomifMs9gyR88VghrP 0OTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=0x5nF2JJP1eGXlFpgowJQPsoOikoM/IeYie683hIioI=; b=GEny144ZEcklLo80P0lEBSUON/+DYEp0qMgWm46OyesZ8qMJ13+3z0mCEigmWYNirG t5NfpyOWE631fUQpeLmOgdSZpnIekDExVgNJ4VsbxFc3BX5spGJhPGwqJUOiFsufQ4cO yDO8drSS8ag52fOe6XPjethghVwdfTl80gdDhlxY7QeMb/mseg7kwg0aSA2LLKKbkXfh ctBlhFbunz81UTbzar1EGxDm9BCIfkhr60xDOqVxiiZb+GuNSaX4ETXsSKVXgwsSxF/O hKCd0kItdo9YpzNJkreitRm5NEi8b8Td/V2swTuc6i9JAhE5XcVsfzU2Pmcq+B7gVo3o sLyA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=yhEkNwLb; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u4si19678416edo.323.2020.12.28.05.19.21; Mon, 28 Dec 2020 05:19:44 -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; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=yhEkNwLb; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731572AbgL1NRc (ORCPT + 99 others); Mon, 28 Dec 2020 08:17:32 -0500 Received: from mail.kernel.org ([198.145.29.99]:45380 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731549AbgL1NRZ (ORCPT ); Mon, 28 Dec 2020 08:17:25 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 2A1642076D; Mon, 28 Dec 2020 13:17:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1609161429; bh=HAaUaajR84gIA9vDyPTHnXJOC9zOSbX8JjPBxpf8Y+o=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=yhEkNwLbc9YTfbiAwNTFx2lnJun+yhxcgPddkkhKskC3GTuRcqa2cBW2PhMnDxFAt O4U45UEACQAiXO8WTajHXP+NK31yi2DnHa/OPwV0oM/3zCOWa1TK67483kVVSV9+7+ 6Kk54V1b6e/duNFrm99QbgCaz9G+qEbldE5le5SM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Dan Sneddon , Nicolas Ferre , Alexandre Belloni , Cristian Birsan Subject: [PATCH 4.14 211/242] ARM: dts: at91: sama5d2: fix CAN message ram offset and size Date: Mon, 28 Dec 2020 13:50:16 +0100 Message-Id: <20201228124915.056617198@linuxfoundation.org> X-Mailer: git-send-email 2.29.2 In-Reply-To: <20201228124904.654293249@linuxfoundation.org> References: <20201228124904.654293249@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Nicolas Ferre commit 85b8350ae99d1300eb6dc072459246c2649a8e50 upstream. CAN0 and CAN1 instances share the same message ram configured at 0x210000 on sama5d2 Linux systems. According to current configuration of CAN0, we need 0x1c00 bytes so that the CAN1 don't overlap its message ram: 64 x RX FIFO0 elements => 64 x 72 bytes 32 x TXE (TX Event FIFO) elements => 32 x 8 bytes 32 x TXB (TX Buffer) elements => 32 x 72 bytes So a total of 7168 bytes (0x1C00). Fix offset to match this needed size. Make the CAN0 message ram ioremap match exactly this size so that is easily understandable. Adapt CAN1 size accordingly. Fixes: bc6d5d7666b7 ("ARM: dts: at91: sama5d2: add m_can nodes") Reported-by: Dan Sneddon Signed-off-by: Nicolas Ferre Signed-off-by: Alexandre Belloni Tested-by: Cristian Birsan Cc: stable@vger.kernel.org # v4.13+ Link: https://lore.kernel.org/r/20201203091949.9015-1-nicolas.ferre@microchip.com Signed-off-by: Greg Kroah-Hartman --- arch/arm/boot/dts/sama5d2.dtsi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --- a/arch/arm/boot/dts/sama5d2.dtsi +++ b/arch/arm/boot/dts/sama5d2.dtsi @@ -1294,7 +1294,7 @@ can0: can@f8054000 { compatible = "bosch,m_can"; - reg = <0xf8054000 0x4000>, <0x210000 0x4000>; + reg = <0xf8054000 0x4000>, <0x210000 0x1c00>; reg-names = "m_can", "message_ram"; interrupts = <56 IRQ_TYPE_LEVEL_HIGH 7>, <64 IRQ_TYPE_LEVEL_HIGH 7>; @@ -1485,7 +1485,7 @@ can1: can@fc050000 { compatible = "bosch,m_can"; - reg = <0xfc050000 0x4000>, <0x210000 0x4000>; + reg = <0xfc050000 0x4000>, <0x210000 0x3800>; reg-names = "m_can", "message_ram"; interrupts = <57 IRQ_TYPE_LEVEL_HIGH 7>, <65 IRQ_TYPE_LEVEL_HIGH 7>; @@ -1495,7 +1495,7 @@ assigned-clocks = <&can1_gclk>; assigned-clock-parents = <&utmi>; assigned-clock-rates = <40000000>; - bosch,mram-cfg = <0x1100 0 0 64 0 0 32 32>; + bosch,mram-cfg = <0x1c00 0 0 64 0 0 32 32>; status = "disabled"; };