mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: renesas: ironhide: Describe inline ECC carveouts
Date: Mon, 13 Jul 2026 12:43:18 +0200	[thread overview]
Message-ID: <1d0d4074-90ca-4b33-9bd3-ff27aa0fd4d4@mailbox.org> (raw)
In-Reply-To: <CAMuHMdUQJ8mzUi0birB5f1KnCMX_QufHTgYB7AW=d3ZoFer+Yg@mail.gmail.com>

On 7/13/26 11:11 AM, Geert Uytterhoeven wrote:

Hello Geert,

>> +               ecc@1e66660000 {
>> +                       reg = <0x1e 0x66660000 0x0 0x999a0000>;
>> +                       no-map;
>> +               };
> 
> Given all DB[0-7]FSDRAMECCAREA00 registers on Ironhide contain
> 0x0000cccc (md.l e98[0-3][7f]450 1), I think the last 3 regions should
> start at offset 0xcccc0000 instead of 0x66660000, too.
> As a bonus, we get 4.8 GiB back ;-)
I asked about that part internally already, and yes, it does take away a 
lot of DRAM. I think it is safer to reserve more DRAM and have a stable 
system than reserve less DRAM and deal with potential stability issues. 
I also think we can always update the reserved memory nodes in the 
future and shrink them to make more DRAM available, once we know that it 
is safe to do so.

  parent reply	other threads:[~2026-07-13 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 16:04 Marek Vasut
2026-07-13  9:11 ` Geert Uytterhoeven
2026-07-13  9:12   ` Geert Uytterhoeven
2026-07-13 10:43   ` Marek Vasut [this message]
2026-07-14  7:50     ` Geert Uytterhoeven

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=1d0d4074-90ca-4b33-9bd3-ff27aa0fd4d4@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@kernel.org \
    --cc=stable@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®