From: Marc Pignat <marc.pignat@hevs.ch>
To: a.zummo@towertech.it
Cc: rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>
Subject: [RFC,PATCH v2] rtc: DS1374 wakeup support
Date: Wed, 30 Jul 2008 10:27:52 +0200 [thread overview]
Message-ID: <200807301027.53074.marc.pignat@hevs.ch> (raw)
Wakeup support implementation.
Signed-off-by: Marc Pignat <marc.pignat@hevs.ch>
---
Hi all!
If your system can wakup using this device, add the I2C_CLIENT_WAKE in your i2c
board info flags, and that's it.
This patch depends on the I2C_CLIENT_WAKE functionnality which is fixed in the
patch '[RFC,PATCH] i2c: fix device_init_wakeup place' (http://lkml.org/lkml/2008/7/29/194).
Changes since v1:
* patch against 2.6.27-rc1
* removed device_init_wakeup(...) calls, they should be handled in i2c-core.c
Best regards
Marc
diff --git a/drivers/rtc/rtc-ds1374.c b/drivers/rtc/rtc-ds1374.c
index 640acd2..b6219c6 100644
--- a/drivers/rtc/rtc-ds1374.c
+++ b/drivers/rtc/rtc-ds1374.c
@@ -429,12 +429,33 @@ static int __devexit ds1374_remove(struct i2c_client *client)
return 0;
}
+#ifdef CONFIG_PM
+static int ds1374_suspend(struct i2c_client *client, pm_message_t state)
+{
+ if (client->irq >= 0 && device_may_wakeup(&client->dev))
+ enable_irq_wake(client->irq);
+ return 0;
+}
+
+static int ds1374_resume(struct i2c_client *client)
+{
+ if (client->irq >= 0 && device_may_wakeup(&client->dev))
+ disable_irq_wake(client->irq);
+ return 0;
+}
+#else
+#define ds1374_suspend NULL
+#define ds1374_resume NULL
+#endif
+
static struct i2c_driver ds1374_driver = {
.driver = {
.name = "rtc-ds1374",
.owner = THIS_MODULE,
},
.probe = ds1374_probe,
+ .suspend = ds1374_suspend,
+ .resume = ds1374_resume,
.remove = __devexit_p(ds1374_remove),
.id_table = ds1374_id,
};
reply other threads:[~2008-07-30 8:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200807301027.53074.marc.pignat@hevs.ch \
--to=marc.pignat@hevs.ch \
--cc=a.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.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®