From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: mvebu: switch to using gpiod API in pm-board code
Date: Mon, 28 Nov 2022 01:13:08 +0100 [thread overview]
Message-ID: <87lenw7x7v.fsf@BL-laptop> (raw)
In-Reply-To: <Y3Qc6et/d+vhd71Q@google.com>
Dmitry Torokhov <dmitry.torokhov@gmail.com> writes:
> This switches PM code to use the newer gpiod API instead of legacy
> gpio API that we want to retire.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Applied on mvebu/dt
Thanks,
Gregory
> ---
> arch/arm/mach-mvebu/pm-board.c | 28 +++++++++-------------------
> 1 file changed, 9 insertions(+), 19 deletions(-)
>
> diff --git a/arch/arm/mach-mvebu/pm-board.c b/arch/arm/mach-mvebu/pm-board.c
> index 7fa1806acd65..beec22e17e89 100644
> --- a/arch/arm/mach-mvebu/pm-board.c
> +++ b/arch/arm/mach-mvebu/pm-board.c
> @@ -8,19 +8,19 @@
> */
>
> #include <linux/delay.h>
> -#include <linux/gpio.h>
> +#include <linux/err.h>
> +#include <linux/gpio/consumer.h>
> #include <linux/init.h>
> #include <linux/io.h>
> #include <linux/of.h>
> #include <linux/of_address.h>
> -#include <linux/of_gpio.h>
> #include <linux/slab.h>
> #include "common.h"
>
> #define ARMADA_PIC_NR_GPIOS 3
>
> static void __iomem *gpio_ctrl;
> -static int pic_gpios[ARMADA_PIC_NR_GPIOS];
> +static struct gpio_desc *pic_gpios[ARMADA_PIC_NR_GPIOS];
> static int pic_raw_gpios[ARMADA_PIC_NR_GPIOS];
>
> static void mvebu_armada_pm_enter(void __iomem *sdram_reg, u32 srcmd)
> @@ -90,27 +90,17 @@ static int __init mvebu_armada_pm_init(void)
> char *name;
> struct of_phandle_args args;
>
> - pic_gpios[i] = of_get_named_gpio(np, "ctrl-gpios", i);
> - if (pic_gpios[i] < 0) {
> - ret = -ENODEV;
> - goto out;
> - }
> -
> name = kasprintf(GFP_KERNEL, "pic-pin%d", i);
> if (!name) {
> ret = -ENOMEM;
> goto out;
> }
>
> - ret = gpio_request(pic_gpios[i], name);
> - if (ret < 0) {
> - kfree(name);
> - goto out;
> - }
> -
> - ret = gpio_direction_output(pic_gpios[i], 0);
> - if (ret < 0) {
> - gpio_free(pic_gpios[i]);
> + pic_gpios[i] = fwnode_gpiod_get_index(of_fwnode_handle(np),
> + "ctrl", i, GPIOD_OUT_HIGH,
> + name);
> + ret = PTR_ERR_OR_ZERO(pic_gpios[i]);
> + if (ret) {
> kfree(name);
> goto out;
> }
> @@ -118,7 +108,7 @@ static int __init mvebu_armada_pm_init(void)
> ret = of_parse_phandle_with_fixed_args(np, "ctrl-gpios", 2,
> i, &args);
> if (ret < 0) {
> - gpio_free(pic_gpios[i]);
> + gpiod_put(pic_gpios[i]);
> kfree(name);
> goto out;
> }
> --
> 2.38.1.431.g37b22c650d-goog
>
>
> --
> Dmitry
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2022-11-28 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 23:12 [PATCH] ARM: mvebu: switch to using gpiod API in pm-board code Dmitry Torokhov
2022-11-16 1:10 ` Andrew Lunn
2022-11-16 1:40 ` Dmitry Torokhov
2022-11-16 2:03 ` Andrew Lunn
2022-11-16 2:03 ` Andrew Lunn
2022-11-28 0:13 ` Gregory CLEMENT [this message]
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=87lenw7x7v.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.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