From: Ralf Baechle <ralf@linux-mips.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Wu Zhangjin <wuzhangjin@gmail.com>,
linux-mips@linux-mips.org, yanh@lemote.com, huhb@lemote.com,
Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH -queue 1/2] [loongson] 2f: add suspend support framework
Date: Thu, 12 Nov 2009 20:03:21 +0100 [thread overview]
Message-ID: <20091112190321.GA2887@linux-mips.org> (raw)
In-Reply-To: <20091111103304.GB26423@elf.ucw.cz>
On Wed, Nov 11, 2009 at 11:33:04AM +0100, Pavel Machek wrote:
> On Wed 2009-11-11 14:57:05, Wu Zhangjin wrote:
> > (Add CC to Rafael J. Wysocki, Len Brown and Pavel Machek)
> >
> > This patch add basic suspend support for loongson2f family machines,
> > loongson2f have a specific feature: when we set it's frequency to ZERO,
> > it will go into a wait mode, and then can be waked up by the external
> > interrupt. so, if we setup suitable interrupts before putting it into
> > wait mode, we will be able wake it up whenever we want via sending the
> > relative interrupts to it.
> >
> > These interrupts are board-specific, Yeeloong2F use the keyboard
> > interrupt and SCI interrupt, but LingLoong and Fuloong2F use the
> > interrupts connected to the processors directly. and BTW: some old
> > LingLoong and FuLoong2F have no such interrupts connected, so, there is
> > no way to wake them up from suspend mode. and therefore, please do not
> > enable the kernel support for them.
> >
> > The board-specific support will be added in the coming patches.
> >
> > Signed-off-by: Wu Zhangjin <wuzhangjin@gmail.com>
>
> Comments are slighlty "interesting", but otherwise it looks ok.
>
> > + /* stop all perf counters */
> > + stop_perf_counters();
>
> This is not exactly useful comment, right?
>
> > + /* mach specific suspend */
> > + mach_suspend();
> ...
> > + /* mach specific resume */
> > + mach_resume();
>
>
> It is probably ok, but you may want to avoid them in future.
>
> ACK.
Thanks. Queued for 2.6.33 with the comments cleaned up.
Ralf
next prev parent reply other threads:[~2009-11-12 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 6:52 [PATCH -queue 0/2] add suspend support for loongson2f Wu Zhangjin
[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 [this message]
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
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=20091112190321.GA2887@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=huhb@lemote.com \
--cc=len.brown@intel.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=wuzhangjin@gmail.com \
--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).