From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/02] ARM: shmobile: R-car Gen2 CMA reservation support
Date: Tue, 10 Jun 2014 06:57:37 +0000 [thread overview]
Message-ID: <20140610065731.GA29303@verge.net.au> (raw)
In-Reply-To: <20140609123837.31532.85914.sendpatchset@w520>
On Tue, Jun 10, 2014 at 01:10:39PM +0900, Magnus Damm wrote:
> Hi Simon,
>
> On Tue, Jun 10, 2014 at 10:37 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Mon, Jun 09, 2014 at 09:38:37PM +0900, Magnus Damm wrote:
> >> ARM: shmobile: R-car Gen2 CMA reservation support
> >>
> >> [PATCH 01/02] ARM: shmobile: Add shared R-Car Gen2 CMA reservation code
> >> [PATCH 02/02] ARM: shmobile: Enable R-Car Gen2 CMA code in board files
> >>
> >> These patches add CMA reservation code for R-Car Gen2 SoCs and boards.
> >>
> >> Instead of using custom memory reservation hacks for demos and other
> >> things, make use of standard CMA to reserve a pool of memory. This memory
> >> is suitable for devices that take physically contiguous memory such as
> >> DU and VSP1 multimedia devices. At this point no device assignment is
> >> included - only memory reservation code is added for now.
> >>
> >> All R-Car Gen2 SoCs so far have LPAE support and boards tend to use more
> >> than 32-bits of physical addresses to access the system memory. These
> >> patches add code that during run time parses the DT memory banks and nick
> >> 256MiB from the highest memory bank within the legacy 32-bit physical memory
> >> space and use that for CMA.
> >>
> >> On Lager and Koelsch boards these 256 MiB is at 0x7000000 -> 0x7fffffff.
> >>
> >> The code uses dynamic calculation of the CMA area base address over static
> >> DT reservation since this kind of configuration is based on software policy.
> >> DT is however still used to describe the system memory banks as expected.
> >> Software memory partitioning is excluded from DT by design.
> >>
> >> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> >
> > Hi Magnus,
> >
> > this seems clean to me. Shall I queue it up?
>
> Thanks, yes please queue up!
Thanks, done.
prev parent reply other threads:[~2014-06-10 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 12:38 [PATCH 00/02] ARM: shmobile: R-car Gen2 CMA reservation support Magnus Damm
2014-06-10 1:37 ` Simon Horman
2014-06-10 4:10 ` Magnus Damm
2014-06-10 6:57 ` Simon Horman [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=20140610065731.GA29303@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).