From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 1/2] gpiolib: of: Prepare of_mm_gpiochip_add_data() for fwnode
Date: Wed, 9 Nov 2022 13:19:30 -0800 [thread overview]
Message-ID: <Y2wZYuadSwbqxpge@google.com> (raw)
In-Reply-To: <20221109150734.38874-1-andriy.shevchenko@linux.intel.com>
On Wed, Nov 09, 2022 at 05:07:33PM +0200, Andy Shevchenko wrote:
> GPIO library is getting rid of of_node, fwnode should be utilized instead.
> Prepare of_mm_gpiochip_add_data() for fwnode.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/gpio/gpiolib-of.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c
> index 4be3c21aa718..feeb9e8e846d 100644
> --- a/drivers/gpio/gpiolib-of.c
> +++ b/drivers/gpio/gpiolib-of.c
> @@ -919,14 +919,15 @@ int of_mm_gpiochip_add_data(struct device_node *np,
> struct of_mm_gpio_chip *mm_gc,
> void *data)
> {
> + struct fwnode_handle *fwnode = of_fwnode_handle(np);
> int ret = -ENOMEM;
> struct gpio_chip *gc = &mm_gc->gc;
>
> - gc->label = kasprintf(GFP_KERNEL, "%pOF", np);
> + gc->label = kasprintf(GFP_KERNEL, "%pfw", fwnode);
> if (!gc->label)
> goto err0;
>
> - mm_gc->regs = of_iomap(np, 0);
> + mm_gc->regs = fwnode_iomap(fwnode, 0);
> if (!mm_gc->regs)
> goto err1;
>
> @@ -935,8 +936,8 @@ int of_mm_gpiochip_add_data(struct device_node *np,
> if (mm_gc->save_regs)
> mm_gc->save_regs(mm_gc);
>
> - of_node_put(mm_gc->gc.of_node);
> - mm_gc->gc.of_node = of_node_get(np);
> + fwnode_handle_put(mm_gc->gc.fwnode);
> + mm_gc->gc.fwnode = fwnode_handle_get(fwnode);
Can we reduce the patch to
fwnode_handle_put(mm_gc->gc.fwnode);
mm_gc->gc.fwnode = fwnode_handle_get(of_fwnode_handle(np));
?
I do not see a reason for converting the rest of invocations to fwnode
given that this is clearly an OF API.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2022-11-09 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 15:07 [PATCH v1 1/2] gpiolib: of: Prepare of_mm_gpiochip_add_data() for fwnode Andy Shevchenko
2022-11-09 15:07 ` [PATCH v1 2/2] gpiolib: of: Drop redundant check in of_mm_gpiochip_remove() Andy Shevchenko
2022-11-09 21:13 ` Dmitry Torokhov
2022-11-09 15:16 ` [PATCH v1 1/2] gpiolib: of: Prepare of_mm_gpiochip_add_data() for fwnode Andy Shevchenko
2022-11-09 21:19 ` Dmitry Torokhov [this message]
2022-11-10 13:56 ` Andy Shevchenko
2022-11-10 10:11 ` 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=Y2wZYuadSwbqxpge@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 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.