From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: linux-kernel@vger.kernel.org Cc: linux-renesas-soc@vger.kernel.org, Wolfram Sang <wsa+renesas@sang-engineering.com>, Linus Walleij <linus.walleij@linaro.org>, Michal Simek <michal.simek@xilinx.com>, linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH 6/6] gpio: gpio-zynq: simplify getting .driver_data Date: Sun, 21 Oct 2018 22:00:01 +0200 [thread overview] Message-ID: <20181021200002.1472-7-wsa+renesas@sang-engineering.com> (raw) In-Reply-To: <20181021200002.1472-1-wsa+renesas@sang-engineering.com> 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 <wsa+renesas@sang-engineering.com> --- Build tested only. buildbot is happy. drivers/gpio/gpio-zynq.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/gpio/gpio-zynq.c b/drivers/gpio/gpio-zynq.c index 3f5fcdd5a429..ac9b02c9598f 100644 --- 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); } -- 2.19.0
WARNING: multiple messages have this Message-ID (diff)
From: wsa+renesas@sang-engineering.com (Wolfram Sang) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 6/6] gpio: gpio-zynq: simplify getting .driver_data Date: Sun, 21 Oct 2018 22:00:01 +0200 [thread overview] Message-ID: <20181021200002.1472-7-wsa+renesas@sang-engineering.com> (raw) In-Reply-To: <20181021200002.1472-1-wsa+renesas@sang-engineering.com> 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 <wsa+renesas@sang-engineering.com> --- Build tested only. buildbot is happy. drivers/gpio/gpio-zynq.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/gpio/gpio-zynq.c b/drivers/gpio/gpio-zynq.c index 3f5fcdd5a429..ac9b02c9598f 100644 --- 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); } -- 2.19.0
next prev parent reply other threads:[~2018-10-21 20:00 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-21 19:59 [PATCH 0/6] gpio: simplify getting .driver_data Wolfram Sang 2018-10-21 19:59 ` Wolfram Sang 2018-10-21 19:59 ` [PATCH 1/6] gpio: gpio-dwapb: " Wolfram Sang 2018-10-30 13:12 ` Linus Walleij 2018-10-21 19:59 ` [PATCH 2/6] gpio: gpio-lynxpoint: " Wolfram Sang 2018-10-30 13:14 ` Linus Walleij 2018-10-21 19:59 ` [PATCH 3/6] gpio: gpio-mxc: " Wolfram Sang 2018-10-30 13:15 ` Linus Walleij 2018-10-21 19:59 ` [PATCH 4/6] gpio: gpio-omap: " Wolfram Sang 2018-10-22 18:30 ` Grygorii Strashko 2018-10-22 18:30 ` Grygorii Strashko 2018-10-30 13:18 ` Linus Walleij 2018-10-21 20:00 ` [PATCH 5/6] gpio: gpio-tegra: " Wolfram Sang 2018-10-22 8:01 ` Thierry Reding 2018-10-30 13:20 ` Linus Walleij 2018-10-21 20:00 ` Wolfram Sang [this message] 2018-10-21 20:00 ` [PATCH 6/6] gpio: gpio-zynq: " Wolfram Sang 2018-10-30 13:19 ` Linus Walleij 2018-10-30 13:19 ` Linus Walleij
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=20181021200002.1472-7-wsa+renesas@sang-engineering.com \ --to=wsa+renesas@sang-engineering.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=michal.simek@xilinx.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.