mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: sameo@linux.intel.com, jedu@slimlogic.co.uk, lrg@slimlogic.co.uk,
	broonie@opensource.wolfsonmicro.com, gg@slimlogic.co.uk,
	linux-kernel@vger.kernel.org
Cc: linux-tegra@vger.kernel.org, ldewangan@nvidia.com
Subject: [PATCH V1] mfd: tps65910: Add wakeup support
Date: Fri, 20 Jan 2012 16:39:30 +0530	[thread overview]
Message-ID: <1327057770-6688-1-git-send-email-ldewangan@nvidia.com> (raw)

Adding wakeup support for PMIC device 65910. This can be
selected through the board specific platform data.

The wakeup should enabled if PMIC need to be configure for
waking up system through RTC or ONKEY.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
This patch will enable the wakeup functionality through
device tps65910/tps65911.

 drivers/mfd/tps65910-irq.c   |    9 +++++++++
 drivers/mfd/tps65910.c       |    1 +
 include/linux/mfd/tps65910.h |    2 ++
 3 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/drivers/mfd/tps65910-irq.c b/drivers/mfd/tps65910-irq.c
index a56be93..8b6f423 100644
--- a/drivers/mfd/tps65910-irq.c
+++ b/drivers/mfd/tps65910-irq.c
@@ -210,6 +210,15 @@ int tps65910_irq_init(struct tps65910 *tps65910, int irq,
 	if (ret != 0)
 		dev_err(tps65910->dev, "Failed to request IRQ: %d\n", ret);
 
+	if (!ret && pdata->en_wakeup) {
+		device_init_wakeup(tps65910->dev, 1);
+		ret = enable_irq_wake(irq);
+		if (ret < 0)
+			dev_warn(tps65910->dev, "Can't enable IRQ as wake "
+				"source: %d\n", ret);
+		return 0;
+	}
+
 	return ret;
 }
 
diff --git a/drivers/mfd/tps65910.c b/drivers/mfd/tps65910.c
index 8517481..88e3dec 100644
--- a/drivers/mfd/tps65910.c
+++ b/drivers/mfd/tps65910.c
@@ -169,6 +169,7 @@ static int tps65910_i2c_probe(struct i2c_client *i2c,
 
 	init_data->irq = pmic_plat_data->irq;
 	init_data->irq_base = pmic_plat_data->irq_base;
+	init_data->en_wakeup = pmic_plat_data->en_wakeup;
 
 	tps65910_gpio_init(tps65910, pmic_plat_data->gpio_base);
 
diff --git a/include/linux/mfd/tps65910.h b/include/linux/mfd/tps65910.h
index d0cb12e..ba8eb6a 100644
--- a/include/linux/mfd/tps65910.h
+++ b/include/linux/mfd/tps65910.h
@@ -777,6 +777,7 @@ struct tps65910_board {
 	int gpio_base;
 	int irq;
 	int irq_base;
+	int en_wakeup;
 	int vmbch_threshold;
 	int vmbch2_threshold;
 	struct regulator_init_data *tps65910_pmic_init_data[TPS65910_NUM_REGS];
@@ -813,6 +814,7 @@ struct tps65910 {
 struct tps65910_platform_data {
 	int irq;
 	int irq_base;
+	int en_wakeup;
 };
 
 int tps65910_set_bits(struct tps65910 *tps65910, u8 reg, u8 mask);
-- 
1.7.1.1


             reply	other threads:[~2012-01-20 11:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 11:09 Laxman Dewangan [this message]
2012-01-20 12:51 ` Mark Brown
2012-01-20 13:00   ` Laxman Dewangan
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=1327057770-6688-1-git-send-email-ldewangan@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

all inboxes | Powered by JetHome®