Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Philby John <pjohn@in.mvista.com>,
	Russell King <rmk@arm.linux.org.uk>
Subject: linux-next: manual merge of the catalin tree with the arm-current tree
Date: Mon, 2 Nov 2009 14:12:04 +1100	[thread overview]
Message-ID: <20091102141204.167b4aaa.sfr@canb.auug.org.au> (raw)

Hi Catalin,

Today's linux-next merge of the catalin tree got a conflict in
arch/arm/mach-realview/core.h arch/arm/mach-realview/realview_pb1176.c
between commit 426fcd2a351e4bf662fee9fa2cf2603a48223164 ("ARM: 5774/1:
Fix Realview ARM1176PB board reboot") from the arc-current tree and
commit 35c6a7ecaa2aafd03dd5d62aa11fbc7a12b82520 ("RealView: Add default
memory configuration") from the catalin tree.

Overlapping additions.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc arch/arm/mach-realview/core.h
index 699671f,1398854..0000000
--- a/arch/arm/mach-realview/core.h
+++ b/arch/arm/mach-realview/core.h
@@@ -61,5 -64,7 +64,7 @@@ extern void realview_timer_init(unsigne
  extern int realview_flash_register(struct resource *res, u32 num);
  extern int realview_eth_register(const char *name, struct resource *res);
  extern int realview_usb_register(struct resource *res);
+ extern void realview_fixup(struct machine_desc *mdesc, struct tag *tags,
+ 			   char **from, struct meminfo *meminfo);
 -
 +extern void (*realview_reset)(char);
  #endif
diff --cc arch/arm/mach-realview/realview_pb1176.c
index a6ba147,b1cdd37..0000000
--- a/arch/arm/mach-realview/realview_pb1176.c
+++ b/arch/arm/mach-realview/realview_pb1176.c
@@@ -290,16 -290,18 +290,28 @@@ static struct sys_timer realview_pb1176
  	.init		= realview_pb1176_timer_init,
  };
  
 +static void realview_pb1176_reset(char mode)
 +{
 +	void __iomem *hdr_ctrl = __io_address(REALVIEW_SYS_BASE) +
 +		REALVIEW_SYS_RESETCTL_OFFSET;
 +	void __iomem *rst_hdr_ctrl = __io_address(REALVIEW_SYS_BASE) +
 +		REALVIEW_SYS_LOCK_OFFSET;
 +	__raw_writel(REALVIEW_SYS_LOCKVAL_MASK, rst_hdr_ctrl);
 +	__raw_writel(REALVIEW_PB1176_SYS_LOCKVAL_RSTCTL, hdr_ctrl);
 +}
 +
+ static void realview_pb1176_fixup(struct machine_desc *mdesc,
+ 				  struct tag *tags, char **from,
+ 				  struct meminfo *meminfo)
+ {
+ 	/*
+ 	 * RealView PB1176 only has 128MB of RAM mapped at 0.
+ 	 */
+ 	meminfo->bank[0].start = 0;
+ 	meminfo->bank[0].size = SZ_128M;
+ 	meminfo->nr_banks = 1;
+ }
+ 
  static void __init realview_pb1176_init(void)
  {
  	int i;

                 reply	other threads:[~2009-11-02  3:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20091102141204.167b4aaa.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pjohn@in.mvista.com \
    --cc=rmk@arm.linux.org.uk \
    /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