linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Russell King <rmk@arm.linux.org.uk>,
	Jaecheol Lee <jc.lee@samsung.com>
Subject: linux-next: manual merge of the s5p tree with the arm tree
Date: Wed, 20 Jul 2011 11:35:58 +1000	[thread overview]
Message-ID: <20110720113558.1fb8c2f8392f52c77becf46a@canb.auug.org.au> (raw)

Hi Kukjin,

Today's linux-next merge of the s5p tree got a conflict in
arch/arm/mach-exynos4/pm.c between commits e7089da9567f ("ARM: pm:
samsung: move cpu_suspend into C code") and 29cb3cd208dd ("ARM: pm: allow
suspend finisher to return error codes") from the arm tree and commit
f8ab7d1a953b ("ARM: EXYNOS4: Add save/restore for other ARM registers")
from the s5p tree.

I fixed it up (see below) and can carry the fix as necessary.

BTW, Russell, commit 29cb3cd208dd above changed the return type of
exynos4_cpu_suspend() from void to int but did not add any return
statement ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc arch/arm/mach-exynos4/pm.c
index 533c28f,45f7fd3..0000000
--- a/arch/arm/mach-exynos4/pm.c
+++ b/arch/arm/mach-exynos4/pm.c
@@@ -280,37 -216,11 +216,11 @@@ static struct sleep_save exynos4_l2cc_s
  	SAVE_ITEM(S5P_VA_L2CC + L2X0_AUX_CTRL),
  };
  
+ /* For Cortex-A9 Diagnostic and Power control register */
+ static unsigned int save_arm_register[2];
+ 
 -void exynos4_cpu_suspend(unsigned long arg)
 +static int exynos4_cpu_suspend(unsigned long arg)
  {
- 	unsigned long tmp;
- 	unsigned long mask = 0xFFFFFFFF;
- 
- 	/* Setting Central Sequence Register for power down mode */
- 
- 	tmp = __raw_readl(S5P_CENTRAL_SEQ_CONFIGURATION);
- 	tmp &= ~(S5P_CENTRAL_LOWPWR_CFG);
- 	__raw_writel(tmp, S5P_CENTRAL_SEQ_CONFIGURATION);
- 
- 	/* Setting Central Sequence option Register */
- 
- 	tmp = __raw_readl(S5P_CENTRAL_SEQ_OPTION);
- 	tmp &= ~(S5P_USE_MASK);
- 	tmp |= S5P_USE_STANDBY_WFI0;
- 	__raw_writel(tmp, S5P_CENTRAL_SEQ_OPTION);
- 
- 	/* Clear all interrupt pending to avoid early wakeup */
- 
- 	__raw_writel(mask, (S5P_VA_GIC_DIST + 0x280));
- 	__raw_writel(mask, (S5P_VA_GIC_DIST + 0x284));
- 	__raw_writel(mask, (S5P_VA_GIC_DIST + 0x288));
- 
- 	/* Disable all interrupt */
- 
- 	__raw_writel(0x0, (S5P_VA_GIC_CPU + 0x000));
- 	__raw_writel(0x0, (S5P_VA_GIC_DIST + 0x000));
- 	__raw_writel(mask, (S5P_VA_GIC_DIST + 0x184));
- 	__raw_writel(mask, (S5P_VA_GIC_DIST + 0x188));
- 
  	outer_flush_all();
  
  	/* issue the standby signal into the pm unit. */

             reply	other threads:[~2011-07-20  1:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  1:35 Stephen Rothwell [this message]
2011-07-20  8:04 ` linux-next: manual merge of the s5p tree with the arm tree Russell King
2011-07-20  8:25   ` Stephen Rothwell
2011-07-20 10:38     ` Kukjin Kim
  -- strict thread matches above, loose matches on Subject: below --
2012-01-05  1:09 Stephen Rothwell
2012-01-05  2:34 ` Kukjin Kim
2012-01-04  2:18 Stephen Rothwell
2012-01-04  9:07 ` Russell King
2012-01-05  0:46   ` Kukjin Kim
2011-12-27 23:36 Stephen Rothwell
2011-12-27 23:33 Stephen Rothwell
2011-12-27 23:33 Stephen Rothwell
2011-12-28  8:33 ` Kukjin Kim
2011-12-27 23:21 Stephen Rothwell
2011-12-27 23:17 Stephen Rothwell
2011-12-27 23:07 Stephen Rothwell
2011-12-28  8:01 ` Kukjin Kim
2011-12-05  0:01 Stephen Rothwell
2011-11-22  2:05 Stephen Rothwell
2011-11-22  2:01 Stephen Rothwell
2011-10-11  2:07 Stephen Rothwell
2011-09-22  2:08 Stephen Rothwell
2011-05-23  1:58 Stephen Rothwell
2010-10-17 23:55 Stephen Rothwell
2010-10-18  1:04 ` Kukjin Kim
2010-10-17 23:50 Stephen Rothwell
2010-10-18  0:57 ` Kukjin Kim
2010-10-18 10:39 ` Kukjin Kim
2010-07-30  0:48 Stephen Rothwell

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=20110720113558.1fb8c2f8392f52c77becf46a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jc.lee@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).