From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "sameo@linux.intel.com" <sameo@linux.intel.com>,
"jedu@slimlogic.co.uk" <jedu@slimlogic.co.uk>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V1] mfd: tps65910: Add wakeup support
Date: Fri, 20 Jan 2012 18:30:24 +0530 [thread overview]
Message-ID: <4F196568.1080503@nvidia.com> (raw)
In-Reply-To: <20120120125152.GE18297@opensource.wolfsonmicro.com>
On Friday 20 January 2012 06:21 PM, Mark Brown wrote:
>
>> The wakeup should enabled if PMIC need to be configure for
>> waking up system through RTC or ONKEY.
> Why the platform data? The power management infrastructure provides
> control of this already.
I did not get how the wakeup enabled in power management infrastructure?
My understanding is that we need to call the two apis
device_wakeup_init() and
enable_irq_wake() for enabling the wakeup functionality.
Is there any other API which does the same and I need to call from the
core driver?
next prev parent reply other threads:[~2012-01-20 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 11:09 [PATCH V1] mfd: tps65910: Add wakeup support Laxman Dewangan
2012-01-20 12:51 ` Mark Brown
2012-01-20 13:00 ` Laxman Dewangan [this message]
2012-01-20 13:02 ` Mark Brown
2012-01-20 13:07 ` Laxman Dewangan
2012-01-20 13:13 ` Mark Brown
2012-01-21 8:10 ` Laxman Dewangan
2012-01-21 11:24 ` Laxman Dewangan
2012-01-21 12:51 ` Mark Brown
2012-01-21 12:57 ` Laxman Dewangan
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=4F196568.1080503@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=jedu@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.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).