From: Rob Herring <robh@kernel.org>
To: "Isaac J. Manjarres" <isaacm@codeaurora.org>
Cc: robh+dt@kernel.org, frowand.list@gmail.com,
Patrick Daly <pdaly@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
lmark@codeaurora.org, pratikp@codeaurora.org,
kernel-team@android.com,
"Isaac J. Manjarres" <isaacm@codeaurora.org>
Subject: Re: [PATCH] of: of_reserved_mem: Increase limit on number of reserved regions
Date: Tue, 25 Feb 2020 15:08:30 -0600 [thread overview]
Message-ID: <20200225210830.GA31602@bogus> (raw)
In-Reply-To: <1582567352-4664-1-git-send-email-isaacm@codeaurora.org>
On Mon, 24 Feb 2020 10:02:32 -0800, "Isaac J. Manjarres" wrote:
> From: Patrick Daly <pdaly@codeaurora.org>
>
> Certain SoCs need to support a large amount of reserved memory
> regions. For example, Qualcomm's SM8150 SoC requires that 20
> regions of memory be reserved for a variety of reasons (e.g.
> loading a peripheral subsystem's firmware image into a
> particular space).
>
> When adding more reserved memory regions to cater to different
> usecases, the remaining number of reserved memory regions--12
> to be exact--becomes too small. Thus, double the existing
> limit of reserved memory regions.
>
> Signed-off-by: Patrick Daly <pdaly@codeaurora.org>
> Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
> ---
> drivers/of/of_reserved_mem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied, thanks.
Rob
next prev parent reply other threads:[~2020-02-25 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 18:02 [PATCH] of: of_reserved_mem: Increase limit on number of reserved regions Isaac J. Manjarres
2020-02-25 21:08 ` Rob Herring [this message]
2020-02-26 9:01 ` 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=20200225210830.GA31602@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=isaacm@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=pdaly@codeaurora.org \
--cc=pratikp@codeaurora.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.