Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.

Signed-off-by: Jingoo Han <jg1....@samsung.com>
---
 drivers/video/backlight/adp8870_bl.c |   21 ++++++++++++---------
 1 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/drivers/video/backlight/adp8870_bl.c 
b/drivers/video/backlight/adp8870_bl.c
index 712c25a..b71c4a2 100644
--- a/drivers/video/backlight/adp8870_bl.c
+++ b/drivers/video/backlight/adp8870_bl.c
@@ -947,25 +947,29 @@ static int adp8870_remove(struct i2c_client *client)
        return 0;
 }
 
-#ifdef CONFIG_PM
-static int adp8870_i2c_suspend(struct i2c_client *client, pm_message_t message)
+#ifdef CONFIG_PM_SLEEP
+static int adp8870_i2c_suspend(struct device *dev)
 {
+       struct i2c_client *client = to_i2c_client(dev);
+
        adp8870_clr_bits(client, ADP8870_MDCR, NSTBY);
 
        return 0;
 }
 
-static int adp8870_i2c_resume(struct i2c_client *client)
+static int adp8870_i2c_resume(struct device *dev)
 {
+       struct i2c_client *client = to_i2c_client(dev);
+
        adp8870_set_bits(client, ADP8870_MDCR, NSTBY | BLEN);
 
        return 0;
 }
-#else
-#define adp8870_i2c_suspend NULL
-#define adp8870_i2c_resume NULL
 #endif
 
+static SIMPLE_DEV_PM_OPS(adp8870_i2c_pm_ops, adp8870_i2c_suspend,
+                       adp8870_i2c_resume);
+
 static const struct i2c_device_id adp8870_id[] = {
        { "adp8870", 0 },
        { }
@@ -974,12 +978,11 @@ MODULE_DEVICE_TABLE(i2c, adp8870_id);
 
 static struct i2c_driver adp8870_driver = {
        .driver = {
-               .name = KBUILD_MODNAME,
+               .name   = KBUILD_MODNAME,
+               .pm     = &adp8870_i2c_pm_ops,
        },
        .probe    = adp8870_probe,
        .remove   = adp8870_remove,
-       .suspend = adp8870_i2c_suspend,
-       .resume  = adp8870_i2c_resume,
        .id_table = adp8870_id,
 };
 
-- 
1.7.2.5


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to