aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/watchdog/sch311x_wdt.c
diff options
context:
space:
mode:
authorWolfram Sang <w.sang@pengutronix.de>2011-07-14 06:53:00 -0400
committerWim Van Sebroeck <wim@iguana.be>2011-07-26 17:21:16 -0400
commit2fc5d52b212b58a5b48af19d85cb60971aa1aa4b (patch)
treeb19d4cb19adb0f384a005942050ab0ef8986a1af /drivers/watchdog/sch311x_wdt.c
parent081d83a3393f65adc94fc4240b9926be3054f9dc (diff)
watchdog: remove empty pm-functions
While checking what watchdog drivers usually do in suspend/resume to spot common behaviour for the watchdog framework, I found these drivers which do nothing but add some cruft. Remove it, it is superfluous. New approaches should probably be done with pm_ops anyway. Signed-off-by: Wolfram Sang <w.sang@pengutronix.de> Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
Diffstat (limited to 'drivers/watchdog/sch311x_wdt.c')
-rw-r--r--drivers/watchdog/sch311x_wdt.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/drivers/watchdog/sch311x_wdt.c b/drivers/watchdog/sch311x_wdt.c
index c7cf4b01f58d..029467e34636 100644
--- a/drivers/watchdog/sch311x_wdt.c
+++ b/drivers/watchdog/sch311x_wdt.c
@@ -472,15 +472,10 @@ static void sch311x_wdt_shutdown(struct platform_device *dev)
472 sch311x_wdt_stop(); 472 sch311x_wdt_stop();
473} 473}
474 474
475#define sch311x_wdt_suspend NULL
476#define sch311x_wdt_resume NULL
477
478static struct platform_driver sch311x_wdt_driver = { 475static struct platform_driver sch311x_wdt_driver = {
479 .probe = sch311x_wdt_probe, 476 .probe = sch311x_wdt_probe,
480 .remove = __devexit_p(sch311x_wdt_remove), 477 .remove = __devexit_p(sch311x_wdt_remove),
481 .shutdown = sch311x_wdt_shutdown, 478 .shutdown = sch311x_wdt_shutdown,
482 .suspend = sch311x_wdt_suspend,
483 .resume = sch311x_wdt_resume,
484 .driver = { 479 .driver = {
485 .owner = THIS_MODULE, 480 .owner = THIS_MODULE,
486 .name = DRV_NAME, 481 .name = DRV_NAME,