All of lore.kernel.org
 help / color / mirror / Atom feed
From: Calvin Zhang <calvinzhang.cool@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Calvin Zhang <calvinzhang.cool@gmail.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Frank Rowand <frowand.list@gmail.com>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] of: make MAX_RESERVED_REGIONS configurable
Date: Tue, 16 Nov 2021 06:55:05 +0800	[thread overview]
Message-ID: <YZLlSd9vPXpQFz5b@debian> (raw)
In-Reply-To: <CAL_JsqLtG4m6hqKc0TJs+e8ZBRZSGgOAoumnvg7u_D46i5D_AA@mail.gmail.com>

On Mon, Nov 15, 2021 at 08:05:45AM -0600, Rob Herring wrote:
>On Mon, Nov 15, 2021 at 1:33 AM Calvin Zhang <calvinzhang.cool@gmail.com> wrote:
>>
>> MAX_RESERVED_REGIONS has changed several times. Max reserved regions
>> count grows bigger as more SOC subsystems require reserved regions.
>>
>> Add a Kconfig for it so that when properly configured, the static
>> reserved_mem array consumes less memory on systems with few reserved
>> regions.
>
>Please read prior discussions:
>
>https://lore.kernel.org/all/?q=of+MAX_RESERVED_REGIONS
>
>And these 2 in particular:
>
>https://lore.kernel.org/all/CAL_JsqJQcWsguwfehAoaRf4o-2VqXxSzKzTqg7s4+N1bp=6V5Q@mail.gmail.com/
>https://lore.kernel.org/all/CAL_JsqLGvUYQmCGXLgSO+6kFj2i87dpaTbMGbyu5oMt=eeu35A@mail.gmail.com/
>
OK. I will try to make the array dynamic.

Thanks,
Calvin

      reply	other threads:[~2021-11-16  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  7:32 [PATCH v2] of: make MAX_RESERVED_REGIONS configurable Calvin Zhang
2021-11-15 14:05 ` Rob Herring
2021-11-15 22:55   ` Calvin Zhang [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=YZLlSd9vPXpQFz5b@debian \
    --to=calvinzhang.cool@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.