From: Sudeep Holla <sudeep.holla@arm.com>
To: Zhaoyang Huang <zhaoyang.huang@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"amit.kucheria@linaro.org" <amit.kucheria@linaro.org>
Subject: Re: [PATCH v4 2/2] add property of "linux,wakeup" for juno.dts
Date: Wed, 16 Sep 2015 09:59:16 +0100 [thread overview]
Message-ID: <55F92F64.50904@arm.com> (raw)
In-Reply-To: <CAN2waFukpBgLM-NawcyqRMEbqC_v3VVoPSP=j0sJ6tJ1vMikqw@mail.gmail.com>
Hi Zhaouyang,
On 16/09/15 09:53, Zhaoyang Huang wrote:
> Hi Sudeep,
Please stop top-posting, I have told you many times now in private.
> Sorry for the confusions I made. I am testing the suspend to idle on
> juno, which is similar to suspend to ram, while the difference is the
> cpu will go into idle itself(you can refer the function freeze_enter())
> instead of running cpu_suspend finally. I find that the pl011 can wakeup
> the system by receiving from the tty.
>
No, it shouldn't be allowed to be configured as wakeup if it can't
wakeup from S2R. So please stop sending this patch. I need to see real
use case for PL011 as a wakeup source.
Also, if we go by your definition, we can make any interrupt as wakeup
source. You need to understand that we hardware support for an interrupt
to be a wakeup irq.
Regards,
Sudeep
prev parent reply other threads:[~2015-09-16 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 6:46 [PATCH v4 1/2] modify pl011 driver to let it work as wakeup source Zhaoyang Huang
2015-09-16 6:47 ` [PATCH v4 2/2] add property of "linux,wakeup" for juno.dts Zhaoyang Huang
2015-09-16 8:41 ` Sudeep Holla
[not found] ` <CAN2waFukpBgLM-NawcyqRMEbqC_v3VVoPSP=j0sJ6tJ1vMikqw@mail.gmail.com>
2015-09-16 8:59 ` Sudeep Holla [this message]
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=55F92F64.50904@arm.com \
--to=sudeep.holla@arm.com \
--cc=amit.kucheria@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=zhaoyang.huang@linaro.org \
/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).