public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdtdec: Support parsing multiple /memory nodes
Date: Wed, 29 Nov 2017 14:23:28 +0100	[thread overview]
Message-ID: <20171129142328.60e8970a@karo-electronics.de> (raw)
In-Reply-To: <20171129024545.6860-1-marek.vasut+renesas@gmail.com>

Hi,

On Wed, 29 Nov 2017 03:45:45 +0100 Marek Vasut wrote:
> It is legal to have multiple /memory nodes in a device tree . Currently,
> fdtdec_setup_memory_size() only supports parsing the first node . This
> patch extends the function such that if a particular /memory node does
> no longer have further "reg" entries and CONFIG_NR_DRAM_BANKS still
> allows for more DRAM banks, the code moves on to the next memory node
> and checks it's "reg"s. This makes it possible to handle both systems
>
<nit>
s/it's/its/
</nit>


Lothar Waßmann

      parent reply	other threads:[~2017-11-29 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  2:45 [U-Boot] [PATCH] fdtdec: Support parsing multiple /memory nodes Marek Vasut
2017-11-29  2:58 ` Tom Rini
2017-11-29  3:11   ` Marek Vasut
2017-11-29 13:08 ` Simon Glass
2017-12-07 11:49   ` Simon Glass
2017-11-29 13:23 ` Lothar Waßmann [this message]

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=20171129142328.60e8970a@karo-electronics.de \
    --to=lw@karo-electronics.de \
    --cc=u-boot@lists.denx.de \
    /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