[PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

	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!

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

 arch/arm/boot/dts/sh73a0-kzm9g-reference.dts | 2 +-
 arch/arm/boot/dts/sh73a0-kzm9g.dts           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
1.9.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

[PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

	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!

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

 arch/arm/boot/dts/sh73a0-kzm9g-reference.dts | 2 +-
 arch/arm/boot/dts/sh73a0-kzm9g.dts           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
1.9.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

[PATCH v2 1/2] ARM: shmobile: kzm9g dts: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

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. 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.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
v2:
  - Drop RFC status,
  - We now know the last 8 MiB of RAM is _not_ used for a U-Boot
    splash screen.
---
 arch/arm/boot/dts/sh73a0-kzm9g.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/sh73a0-kzm9g.dts b/arch/arm/boot/dts/sh73a0-kzm9g.dts
index 27c5f426d172f03d..e7dae01933a575f1 100644
--- a/arch/arm/boot/dts/sh73a0-kzm9g.dts
+++ b/arch/arm/boot/dts/sh73a0-kzm9g.dts
@@ -21,6 +21,6 @@
 
 	memory {
 		device_type = "memory";
-		reg = <0x41000000 0x1e800000>;
+		reg = <0x40000000 0x20000000>;
 	};
 };
-- 
1.9.1

[PATCH v2 1/2] ARM: shmobile: kzm9g dts: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

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. 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.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
v2:
  - Drop RFC status,
  - We now know the last 8 MiB of RAM is _not_ used for a U-Boot
    splash screen.
---
 arch/arm/boot/dts/sh73a0-kzm9g.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/sh73a0-kzm9g.dts b/arch/arm/boot/dts/sh73a0-kzm9g.dts
index 27c5f426d172f03d..e7dae01933a575f1 100644
--- a/arch/arm/boot/dts/sh73a0-kzm9g.dts
+++ b/arch/arm/boot/dts/sh73a0-kzm9g.dts
@@ -21,6 +21,6 @@
 
 	memory {
 		device_type = "memory";
-		reg = <0x41000000 0x1e800000>;
+		reg = <0x40000000 0x20000000>;
 	};
 };
-- 
1.9.1

[PATCH v2 2/2] ARM: shmobile: kzm9g-reference dts: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

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. 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.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
v2:
  - Drop RFC status,
  - We now know the last 8 MiB of RAM is _not_ used for a U-Boot
    splash screen.
---
 arch/arm/boot/dts/sh73a0-kzm9g-reference.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts b/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts
index 6d32c87632d42fda..b6c292f839584343 100644
--- a/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts
+++ b/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts
@@ -45,7 +45,7 @@
 
 	memory {
 		device_type = "memory";
-		reg = <0x41000000 0x1e800000>;
+		reg = <0x40000000 0x20000000>;
 	};
 
 	reg_1p8v: regulator@0 {
-- 
1.9.1

[PATCH v2 2/2] ARM: shmobile: kzm9g-reference dts: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

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. 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.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
v2:
  - Drop RFC status,
  - We now know the last 8 MiB of RAM is _not_ used for a U-Boot
    splash screen.
---
 arch/arm/boot/dts/sh73a0-kzm9g-reference.dts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts b/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts
index 6d32c87632d42fda..b6c292f839584343 100644
--- a/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts
+++ b/arch/arm/boot/dts/sh73a0-kzm9g-reference.dts
@@ -45,7 +45,7 @@
 
 	memory {
 		device_type = "memory";
-		reg = <0x41000000 0x1e800000>;
+		reg = <0x40000000 0x20000000>;
 	};
 
 	reg_1p8v: regulator at 0 {
-- 
1.9.1

Re: [PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Simon Horman]

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.

[PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Simon Horman]

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.

Re: [PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Simon Horman]

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.

[PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Simon Horman]

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.

Re: [PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Simon Horman]

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

[PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Simon Horman]

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

Re: [PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

Hi Simon,

On Fri, Jan 23, 2015 at 5:22 AM, Simon Horman <horms@verge.net.au> wrote:
> 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.

OK, Thanks!

> 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

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

[PATCH v2 0/2] ARM: shmobile: kzm9g: Declare the full 512 MiB of RAM

[Geert Uytterhoeven]

Hi Simon,

On Fri, Jan 23, 2015 at 5:22 AM, Simon Horman <horms@verge.net.au> wrote:
> 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.

OK, Thanks!

> 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

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds