All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM
Date: Fri, 23 Jan 2015 04:22:52 +0000	[thread overview]
Message-ID: <20150123042252.GB17548@verge.net.au> (raw)
In-Reply-To: <20150122025141.GG31170@verge.net.au>

On Thu, Jan 22, 2015 at 11:51:42AM +0900, Simon Horman wrote:
> On Thu, Jan 08, 2015 at 09:14:12AM +0900, Simon Horman wrote:
> > On Tue, Jan 06, 2015 at 08:17:37PM +0100, Geert Uytterhoeven wrote:
> > > 	Hi Simon, Magnus,
> > > 
> > > This patch series prepares kzm9g and kzm9g-reference dts for booting a
> > > multi-platform kernel.
> > > 
> > > Traditionally, the first 16 MiB of RAM was reserved for the RT
> > > processor.  However, this is incompatible with CONFIG_AUTO_ZRELADDR=y,
> > > which requires that the start address of physical memory is a multiple
> > > of 128 MiB.
> > > 
> > > As CONFIG_AUTO_ZRELADDR=y is enabled for multi-platform kernels, declare
> > > RAM to start at 0x40000000.
> > > 
> > > While at it, reclaim the last 8 MiB of RAM, too, so the full 512 MiB is
> > > available. We don't know the exact reason why the last 8 MiB of RAM
> > > was reserved, but thanks to Simon we know it is not used for a U-Boot
> > > splash screen.  Note that kzm9g_defconfig still has
> > > CONFIG_MEMORY_START=0x41000000 and CONFIG_MEMORY_SIZE=0x1f000000, so
> > > before the advent of DT we scribbled over the last 8 MiB, too.
> > > 
> > > This is an alternative solution for "[PATCH v2 01/05] ARM: shmobile:
> > > kzm9g-reference: 0x48008000 load address"
> > > (http://www.spinics.net/lists/linux-sh/msg38385.html), which
> > > (a) doesn't loose 112 MiB of RAM, and
> > > (b) doesn't force to switch from zImage to uImage.
> > > 
> > > Thanks for applying!
> > 
> > Thanks, done.
> 
> For the record: Olof has asked for review comments for the BSC driver and
> binding patches. Accordingly I have dropped them, and these patches which
> depend on them, from next.
> 
> This dependency may be due to the way the branches are arranged, rather
> than actual dependencies of the code. But regardless I am dropping all
> effected branches for now.

I have now had a chance to re-examine these patches and it seems to me that
they do not depend on the BSC driver (or anything elsei other than possibly
for context).  With that in mind I have queued them up in the dt-for-v3.21
branch and pushed this as part of renesas-devel-20150123-v3.19-rc5.

Please take a moment to see if what I have done makes sense to you.

For reference this covers the following patches which comprised this series:

Geert Uytterhoeven (2):
  ARM: shmobile: kzm9g dts: Declare the full 512 MiB of RAM
  ARM: shmobile: kzm9g-reference dts: Declare the full 512 MiB of RAM

WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM
Date: Fri, 23 Jan 2015 13:22:52 +0900	[thread overview]
Message-ID: <20150123042252.GB17548@verge.net.au> (raw)
In-Reply-To: <20150122025141.GG31170@verge.net.au>

On Thu, Jan 22, 2015 at 11:51:42AM +0900, Simon Horman wrote:
> On Thu, Jan 08, 2015 at 09:14:12AM +0900, Simon Horman wrote:
> > On Tue, Jan 06, 2015 at 08:17:37PM +0100, Geert Uytterhoeven wrote:
> > > 	Hi Simon, Magnus,
> > > 
> > > This patch series prepares kzm9g and kzm9g-reference dts for booting a
> > > multi-platform kernel.
> > > 
> > > Traditionally, the first 16 MiB of RAM was reserved for the RT
> > > processor.  However, this is incompatible with CONFIG_AUTO_ZRELADDR=y,
> > > which requires that the start address of physical memory is a multiple
> > > of 128 MiB.
> > > 
> > > As CONFIG_AUTO_ZRELADDR=y is enabled for multi-platform kernels, declare
> > > RAM to start at 0x40000000.
> > > 
> > > While at it, reclaim the last 8 MiB of RAM, too, so the full 512 MiB is
> > > available. We don't know the exact reason why the last 8 MiB of RAM
> > > was reserved, but thanks to Simon we know it is not used for a U-Boot
> > > splash screen.  Note that kzm9g_defconfig still has
> > > CONFIG_MEMORY_START=0x41000000 and CONFIG_MEMORY_SIZE=0x1f000000, so
> > > before the advent of DT we scribbled over the last 8 MiB, too.
> > > 
> > > This is an alternative solution for "[PATCH v2 01/05] ARM: shmobile:
> > > kzm9g-reference: 0x48008000 load address"
> > > (http://www.spinics.net/lists/linux-sh/msg38385.html), which
> > > (a) doesn't loose 112 MiB of RAM, and
> > > (b) doesn't force to switch from zImage to uImage.
> > > 
> > > Thanks for applying!
> > 
> > Thanks, done.
> 
> For the record: Olof has asked for review comments for the BSC driver and
> binding patches. Accordingly I have dropped them, and these patches which
> depend on them, from next.
> 
> This dependency may be due to the way the branches are arranged, rather
> than actual dependencies of the code. But regardless I am dropping all
> effected branches for now.

I have now had a chance to re-examine these patches and it seems to me that
they do not depend on the BSC driver (or anything elsei other than possibly
for context).  With that in mind I have queued them up in the dt-for-v3.21
branch and pushed this as part of renesas-devel-20150123-v3.19-rc5.

Please take a moment to see if what I have done makes sense to you.

For reference this covers the following patches which comprised this series:

Geert Uytterhoeven (2):
  ARM: shmobile: kzm9g dts: Declare the full 512 MiB of RAM
  ARM: shmobile: kzm9g-reference dts: Declare the full 512 MiB of RAM

  reply	other threads:[~2015-01-23  4:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 19:17 [PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM Geert Uytterhoeven
2015-01-06 19:17 ` Geert Uytterhoeven
2015-01-06 19:17 ` [PATCH v2 1/2] ARM: shmobile: kzm9g dts: " Geert Uytterhoeven
2015-01-06 19:17   ` Geert Uytterhoeven
2015-01-06 19:17 ` [PATCH v2 2/2] ARM: shmobile: kzm9g-reference " Geert Uytterhoeven
2015-01-06 19:17   ` Geert Uytterhoeven
2015-01-08  0:14 ` [PATCH v2 0/2] ARM: shmobile: kzm9g: " Simon Horman
2015-01-08  0:14   ` Simon Horman
2015-01-22  2:51   ` Simon Horman
2015-01-22  2:51     ` Simon Horman
2015-01-23  4:22     ` Simon Horman [this message]
2015-01-23  4:22       ` Simon Horman
2015-01-23  9:55       ` Geert Uytterhoeven
2015-01-23  9:55         ` 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=20150123042252.GB17548@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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.