From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] Sharp power management: split into sharpsl-dependend and generic parts
Date: Mon, 28 Nov 2005 21:50:23 +0000 [thread overview]
Message-ID: <1133214624.8673.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20051121224706.GA12906@elf.ucw.cz>
On Mon, 2005-11-21 at 23:47 +0100, Pavel Machek wrote:
> Hi!
>
> This splits sharpsl_pm.c into sharpsl_pm.c and
> sharp_pm.c. sharpsl_pm.c contains stuff that is shared between spitz
> and corgi, sharp_pm.c contains more widely usable code. I'd like
> something like this to be eventually merged... [Of course, I'll
> cleanup #ifdef COLLIE's, I did not realize some were still pending.]
As discussed, I've made a version of this available as:
http://www.rpsys.net/openzaurus/patches/sharpsl_pm_move-r0.patch
This:
* moves the common code into arm/common
* adds a sharpsl_pm.h header file (in asm/hardware)
* adds appropriate Kconfig entries for this
* removes all the "nasty" macros
* refactors temperature measurement slightly
* removes most of the led code. I have some led patches which apply
after the patch above to implement that differently
* combined the status and measurement code into a single machine
dependent function.
I know that the pxa_pm_prepare/enter/finish functions are going to be a
problem on collie but will await the rest of Pavel's findings before
trying to work out the best way to handle it.
I've asked the person working on tosa (SL-C6000) to investigate what
changes he needs to the code to enable tosa to work within this
framework as well.
Richard
next prev parent reply other threads:[~2005-11-28 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:47 [PATCH] Sharp power management: split into sharpsl-dependend and generic parts Pavel Machek
2005-11-22 0:37 ` Richard Purdie
2005-11-22 1:17 ` Pavel Machek
2005-11-28 21:50 ` Richard Purdie [this message]
2005-12-01 12:28 ` Pavel Machek
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=1133214624.8673.23.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 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.