Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Manuel Lauss <mlau@msc-ge.com>
To: Dmitri Vorobiev <dmitri.vorobiev@movial.fi>
Cc: Manuel Lauss <mano@roarinelk.homelinux.net>, linux-mips@linux-mips.org
Subject: Re: [PATCH v4 7/10] Alchemy: split core PM code from sysctl parts.
Date: Wed, 30 Jul 2008 10:54:20 +0200	[thread overview]
Message-ID: <48902C3C.9060507@msc-ge.com> (raw)
In-Reply-To: <48901B7A.2070700@movial.fi>

Dmitri Vorobiev wrote:
> Manuel Lauss wrote:
>> The Alchemy power.c file contains both core suspend/resume code, which
>> is processor specific, and leftovers of the 2.4 PM userspace interface
>> (sysctls).
>>
>> This patch moves the userspace interface to the platform.c file and
>> leaves the core board-independent suspend/resume parts which should be
>> usable for all Alchemy-based systems intact.
>>
>> Signed-off-by: Manuel Lauss <mano@roarinelk.homelinux.net>
>> ---
>>  arch/mips/au1000/common/platform.c |  304 ++++++++++++++++++++++++++++++++++-
>>  arch/mips/au1000/common/power.c    |  317 +-----------------------------------
>>  2 files changed, 305 insertions(+), 316 deletions(-)
>>
>> diff --git a/arch/mips/au1000/common/platform.c b/arch/mips/au1000/common/platform.c
>> index 66d6770..1e89560 100644
>> --- a/arch/mips/au1000/common/platform.c
>> +++ b/arch/mips/au1000/common/platform.c
[...]
>> +	/**
>> +	 ** The code below is all system dependent and we should probably
>> +	 ** have a function call out of here to set this up.  You need
>> +	 ** to configure the GPIO or timer interrupts that will bring
>> +	 ** you out of sleep.
>> +	 ** For testing, the TOY counter wakeup is useful.
>> +	 **/
>> +#if 0
> 
> Why not simply remove the dead code while you're at it?

That code is removed by a later patch in the series.  This patch is
just code reshuffling; I wanted to leave everything (as broken) as
it was.

Thanks,
	Manuel Lauss

  reply	other threads:[~2008-07-30  8:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 16:58 [PATCH v4 0/10] Alchemy updates Manuel Lauss
2008-07-29 16:59 ` [PATCH v4 1/10] Alchemy: remove get/set_au1x00_lcd_clock() Manuel Lauss
2008-07-29 17:00 ` [PATCH v4 2/10] Alchemy: remove cpu_table Manuel Lauss
2008-07-29 17:00 ` [PATCH v4 3/10] MIPS: make cp0 counter clocksource/event usable as fallback Manuel Lauss
2008-07-29 17:01 ` [PATCH v4 4/10] Alchemy: RTC counter clocksource / clockevent support Manuel Lauss
2008-07-29 17:02 ` [PATCH v4 5/10] Alchemy: move calc_clock function Manuel Lauss
2008-07-29 17:02 ` [PATCH v4 6/10] Alchemy: compile platform.c only when building for a demoboard Manuel Lauss
2008-07-29 17:03 ` [PATCH v4 7/10] Alchemy: split core PM code from sysctl parts Manuel Lauss
2008-07-30  7:42   ` Dmitri Vorobiev
2008-07-30  8:54     ` Manuel Lauss [this message]
2008-07-30  9:02       ` Dmitri Vorobiev
2008-07-29 17:04 ` [PATCH v4 8/10] Alchemy: Fix PM code for Au1200/Au1550 Manuel Lauss
2008-07-29 17:04 ` [PATCH v4 9/10] Alchemy: dbdma suspend/resume support Manuel Lauss
2008-07-29 17:05 ` [PATCH v4 10/10] Alchemy: new demoboard userspace suspend interface Manuel Lauss
2008-07-29 21:33 ` [PATCH v4 0/10] Alchemy updates Kevin Hickey
2008-07-30 10:28   ` Manuel Lauss
2008-07-30 21:36     ` Kevin Hickey
2008-08-06 20:39 ` Kevin Hickey

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=48902C3C.9060507@msc-ge.com \
    --to=mlau@msc-ge.com \
    --cc=dmitri.vorobiev@movial.fi \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    /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