Devicetree
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Troy Mitchell <troy.mitchell@linux.spacemit.com>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] riscv: dts: spacemit: k3: use com260 8gb memory configuration
Date: Tue, 17 Nov 2026 00:57:55 +0000	[thread overview]
Message-ID: <20261117005755-GKD100890@kernel.org> (raw)
In-Reply-To: <20261115195112.32120-2-e@freeshell.de>

Hi E Shattow,

On 11:50 Sun 15 Nov     , E Shattow wrote:
> The boot loader may override this configuration based on stored ID value
> in EEPROM TLV and if it does not then the smallest common sold
I think bootloader will detect memory size during DDR initiliazation phase,
and then update the DT configuration, I haven't checked vendor code, but
plan to implement this in mainline u-boot..

While the change itself looks good, to have always smallest valid default..

> configuration of 8gb is the most compatible option.
> 
> Signed-off-by: E Shattow <e@freeshell.de>
> ---
>  arch/riscv/boot/dts/spacemit/k3-com260.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/riscv/boot/dts/spacemit/k3-com260.dtsi b/arch/riscv/boot/dts/spacemit/k3-com260.dtsi
> index 054bfff7413a..c18680b963a4 100644
> --- a/arch/riscv/boot/dts/spacemit/k3-com260.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k3-com260.dtsi
> @@ -14,7 +14,7 @@ / {
>  
>  	memory@100000000 {
>  		device_type = "memory";
> -		reg = <0x1 0x00000000 0x4 0x00000000>;
> +		reg = <0x1 0x00000000 0x2 0x00000000>;
>  	};
>  
>  	reg_5v_sys: regulator-5v-sys {
> -- 
> 2.53.0
> 

-- 
Yixun Lan (dlan)

  reply	other threads:[~2026-11-17  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261115195112.32120-1-e@freeshell.de>
2026-11-15 19:50 ` [PATCH 1/2] riscv: dts: spacemit: k3: use com260 8gb memory configuration E Shattow
2026-11-17  0:57   ` Yixun Lan [this message]
2026-11-15 19:51 ` [PATCH 2/2] riscv: dts: spacemit: k3: use pico-itx " E Shattow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261117005755-GKD100890@kernel.org \
    --to=dlan@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=e@freeshell.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    --cc=troy.mitchell@linux.spacemit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox