Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3913751ybc; Thu, 14 Nov 2019 17:12:12 -0800 (PST) X-Google-Smtp-Source: APXvYqzHfef5nUh9Fev7RkVXsc4YsqjxAz5LqR6j4fvhGQpIiegyAckU5rq9qm2z6lN3+RpnrOfA X-Received: by 2002:adf:e50e:: with SMTP id j14mr11314698wrm.179.1573780332329; Thu, 14 Nov 2019 17:12:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573780332; cv=none; d=google.com; s=arc-20160816; b=aj1sbjMXsvxU3KyDnAewrgUoqgIBrlSu953djWddNK3Nq5C3o7a2x3sR85pqGg0OHp n1MAdikxSbDRSTx8cLX/x7F1Efa+cy1r+pb+AoaD3IS7E3rltxHVthUMopxQvPiy2fL6 mwUJBdSXh1iy3N/QFvGwMiyqTJvOma2XdGZAokl3xltbEgvzXcUeukzR5BFnQgr3rIU3 Vd7UUyMlRH65XuFAZnHRUS+0RvR5iITILoxCjQm25f4xQuvw7WlA6dF8dQ+P0JZ00M6r uj7S6J1ZK/HOlOj+4yOHXWKD3o65PeVi6Rizyt98T0Ldebt+fT6DczXVPORCtOOiDiUH QK1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=OCKMRAN181sQ5VNzPIYHH+Kw4WRPPME1nnGwE6Dc4/8=; b=meES4aH7ZWn4OSqiDKvzg0EHE4a1cRttT20qk+3AeXqQQvtThQnH5SNyshc6zkMyEE CH8hqDgSJjmMUdDPVlDkmaUUV23dp/4tjvdoLxw6JQM/SUudisPnKcIAJLcuZHpIoFmr w91gh3aKV8CTnwxjWhJbwWSjSp0Lv6DjBhd/5MkCmx4skLsI+kYfPhAmnts5oUij53uD 00xpBc0Hrryugxzbs0SxAYvHIyuwW/BJZ4cWXqhwGGsX5e2e4XYcWZk+cHWv8kXsr+TX P3XcApKTnhXyv8SqfaEGnai7KriNw6U70EJqsJyWX5ZC7MG+2w7UbNT2QoB4ZApsQNjR Cmzg== 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 a3si4531764ejy.247.2019.11.14.17.11.47; Thu, 14 Nov 2019 17:12:12 -0800 (PST) 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 S1727336AbfKOBIf (ORCPT + 99 others); Thu, 14 Nov 2019 20:08:35 -0500 Received: from mx2.suse.de ([195.135.220.15]:43692 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726996AbfKOBIf (ORCPT ); Thu, 14 Nov 2019 20:08:35 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id DDE13AEAB; Fri, 15 Nov 2019 01:08:33 +0000 (UTC) Subject: Re: [PATCH] arm64: dts: realtek: Add Realtek rtd1619 and mjolnir To: James Tai Cc: "linux-realtek-soc@lists.infradead.org" , "linux-arm-kernel@lists.infradead.org" , "'linux-kernel@vger.kernel.org'" , Mark Rutland , Rob Herring References: <43B123F21A8CFE44A9641C099E4196FFCF91BEFA@RTITMBSVM04.realtek.com.tw> <25fdd8eb-f1a0-82ae-9c4b-22325b163b0e@suse.de> <43B123F21A8CFE44A9641C099E4196FFCF920024@RTITMBSVM04.realtek.com.tw> <7a05ac2c-00bc-b2ac-0a33-be0242d33188@suse.de> <309cd67da48e4702ae3dcc4ca8ab4309@realtek.com> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Organization: SUSE Software Solutions Germany GmbH Message-ID: <279fd3a3-17dc-5796-f0b0-e39eb919081f@suse.de> Date: Fri, 15 Nov 2019 02:08:32 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <309cd67da48e4702ae3dcc4ca8ab4309@realtek.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi James, Am 11.11.19 um 03:58 schrieb James Tai: >> How much? More than 0x98000000? The RTD1395 datasheet says up to 4 GB - >> does that mean it continues in a second region beyond 0xffffffff? Those >> locations should be excluded in the soc node ranges (which you sadly appear to >> have dropped in v2). > > Sorry for my misunderstanding. The RAM region don't require > two cells for memory nodes, so I'll fix it in v3 patch. Should I then also change RTD1395 to use only one cell, or does it support more RAM than RTD1619? By my calculation 0x98000000 is less than 2.4 GiB! So, does RAM continue between r-bus and GIC, similar to how it does on RTD1195? Then we need to exclude those RAM ranges from the SoC node (adjusting 0x68000000). Regards, Andreas -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)