From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, yanh@lemote.com, huhb@lemote.com,
Wu Zhangjin <wuzhangjin@gmail.com>
Subject: [PATCH -queue 0/2] add suspend support for loongson2f
Date: Wed, 11 Nov 2009 14:52:35 +0800 [thread overview]
Message-ID: <cover.1257920162.git.wuzhangjin@gmail.com> (raw)
Loongson2f's cpu frequency is software configurable, when we set its frequency
to ZERO, it will go into the suspend mode and can be waked up by the external
interrupts.
With this feature and based on the kernel's suspend framework, this patch add
the suspend support for loongson2f family machines.
To utilize this support, the machines should provide a necessary external
interrupt to wakeup loongson2f from the suspend mode and make sure the
interrupt be able to send to the processor directly or indirectly(the interrupt
path is not blocked). otherwise, it will suspend there all the time.
And If there is an external timer used, please mask it with IRQF_TIMER,
otherwise, the system will fail on resuming from suspend.
The old lemote Fuloong2F mini PC did not provide any method to wakeup the
machine from the suspend mode, so, please not try to suspend the machine. But
the latest lemote Fuloong2F add an interrupt line from the Power Button to the
Processor, If we press the button and release it immediatly, it will work as a
wakeup button.
For YeeLoong2F netbook, Since it's easy to setup the keyboard interrupt as the
wakeup interrupt, we just setup it and avoid changing the hardware. So the old
YeeLoong2F machines can also utilize this support. and in the coming patchset,
we will also setup the LID interrupt as the wakeup interrupt.
Thanks & Regards,
Wu Zhangjin
Wu Zhangjin (2):
[loongson] 2f: add suspend support framework
[loongson] yeeloong2f: add board specific suspend support
arch/mips/loongson/Kconfig | 5 +
arch/mips/loongson/common/Makefile | 6 ++
arch/mips/loongson/common/pm.c | 157 +++++++++++++++++++++++++++++++++
arch/mips/loongson/lemote-2f/Makefile | 6 ++
arch/mips/loongson/lemote-2f/pm.c | 70 +++++++++++++++
5 files changed, 244 insertions(+), 0 deletions(-)
create mode 100644 arch/mips/loongson/common/pm.c
create mode 100644 arch/mips/loongson/lemote-2f/pm.c
next reply other threads:[~2009-11-11 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 6:52 Wu Zhangjin [this message]
[not found] ` <cover.1257922151.git.wuzhangjin@gmail.com>
2009-11-11 6:52 ` [PATCH -queue 1/2] [loongson] 2f: add suspend support framework Wu Zhangjin
2009-11-11 9:41 ` Ralf Baechle
2009-11-11 11:00 ` Ralf Baechle
2009-11-11 6:52 ` [PATCH -queue 2/2] [loongson] yeeloong2f: add board specific suspend support Wu Zhangjin
2009-11-11 6:57 ` [PATCH -queue 1/2] [loongson] 2f: add suspend support framework Wu Zhangjin
2009-11-11 10:33 ` Pavel Machek
2009-11-11 15:32 ` Wu Zhangjin
2009-11-12 19:03 ` Ralf Baechle
2009-11-11 6:57 ` [PATCH -queue 2/2] [loongson] yeeloong2f: add board specific suspend support Wu Zhangjin
2009-11-11 10:33 ` Pavel Machek
2009-11-12 19:03 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2009-11-11 6:55 [PATCH -queue 0/2] add suspend support for loongson2f Wu Zhangjin
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=cover.1257920162.git.wuzhangjin@gmail.com \
--to=wuzhangjin@gmail.com \
--cc=huhb@lemote.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=yanh@lemote.com \
/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).