Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <2beb9364-7b5d-4cf7-9003-2d70122731c3@gmail.com>
Date:   Wed, 12 Jul 2023 19:07:00 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.12.0
Subject: Re: [PATCH] ARM: dts: BCM5301X: Extend RAM to full 256MB for Linksys
 EA6500 V2
To:     Andrew Lunn <andrew@lunn.ch>,
        Christian Marangi <ansuelsmth@gmail.com>
Cc:     Florian Fainelli <florian.fainelli@broadcom.com>,
        Hauke Mehrtens <hauke@hauke-m.de>,
        Broadcom internal kernel review list 
        <bcm-kernel-feedback-list@broadcom.com>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        =?UTF-8?Q?Ren=c3=a9_Kjellerup?= <rk.katana.steel@gmail.com>,
        linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        Aleksey Nasibulin <alealexpro100@ya.ru>, stable@vger.kernel.org
References: <20230712014017.28123-1-ansuelsmth@gmail.com>
 <fc94da45-aba8-4e69-a1a0-c1d58a90c68c@lunn.ch>
Content-Language: en-US
From:   =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= <zajec5@gmail.com>
In-Reply-To: <fc94da45-aba8-4e69-a1a0-c1d58a90c68c@lunn.ch>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 12.07.2023 17:23, Andrew Lunn wrote:
>> --- a/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6500-v2.dts
>> +++ b/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6500-v2.dts
>> @@ -19,7 +19,8 @@ chosen {
>>   
>>   	memory@0 {
>>   		device_type = "memory";
>> -		reg = <0x00000000 0x08000000>;
>> +		reg = <0x00000000 0x08000000>,
>> +		      <0x88000000 0x08000000>;
> 
> So there is a hole in the middle? Does this require any special
> CONFIG_ option to support sparse memory?

This is how RAM is mapped on all known Northstar devices. Using two
blocks.

I've heard there is a way to design Northstar SoC board to have all RAM
in one region but thay requires disabling something (I don't remember
what) and in practice to vendor decided to do that.

AFAIK no extra CONFIG_* option is needed to make Linux map multiple RAM
regions.