gpio: gpio-zynq: simplify getting .driver_data

We should get 'driver_data' from 'struct device' directly. Going via
platform_device is an unneeded step back and forth.

Signed-off-by: Wolfram Sang <[email protected]>
Signed-off-by: Linus Walleij <[email protected]>

diff --git a/drivers/gpio/gpio-zynq.c b/drivers/gpio/gpio-zynq.c
index 3f5fcdd5a4291dd41c35e5032122a4b39873686d..ac9b02c9598f5e9827b9e8b28f7ad04edff681f3 100644 (file)
--- a/drivers/gpio/gpio-zynq.c
+++ b/drivers/gpio/gpio-zynq.c
@@ -693,8 +693,7 @@ static int __maybe_unused zynq_gpio_resume(struct device *dev)
 
 static int __maybe_unused zynq_gpio_runtime_suspend(struct device *dev)
 {
-       struct platform_device *pdev = to_platform_device(dev);
-       struct zynq_gpio *gpio = platform_get_drvdata(pdev);
+       struct zynq_gpio *gpio = dev_get_drvdata(dev);
 
        clk_disable_unprepare(gpio->clk);
 
@@ -703,8 +702,7 @@ static int __maybe_unused zynq_gpio_runtime_suspend(struct device *dev)
 
 static int __maybe_unused zynq_gpio_runtime_resume(struct device *dev)
 {
-       struct platform_device *pdev = to_platform_device(dev);
-       struct zynq_gpio *gpio = platform_get_drvdata(pdev);
+       struct zynq_gpio *gpio = dev_get_drvdata(dev);
 
        return clk_prepare_enable(gpio->clk);
 }