From: Philipp Zabel <p.zabel@pengutronix.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 9/9] reset: gpio: use software nodes to setup the GPIO lookup
Date: Mon, 06 Oct 2025 17:55:05 +0200 [thread overview]
Message-ID: <e6a120d4ada6d032f69812f14a7e794ac1796a85.camel@pengutronix.de> (raw)
In-Reply-To: <20251006-reset-gpios-swnodes-v1-9-6d3325b9af42@linaro.org>
On Mo, 2025-10-06 at 15:00 +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> GPIO machine lookup is a nice mechanism for associating GPIOs with
> consumers if we don't know what kind of device the GPIO provider is or
> when it will become available. However in the case of the reset-gpio, we
> are already holding a reference to the device and so can reference its
> firmware node. Let's setup a software node that references the relevant
> GPIO and attach it to the auxiliary device we're creating.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> drivers/reset/core.c | 132 ++++++++++++++++++++++++++++++---------------------
> 1 file changed, 78 insertions(+), 54 deletions(-)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index c9f13020ca3a7b9273488497a7d4240d0af762b0..b3e6ba7a9c3d756d2e30dc20edda9c02b624aefd 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
[...]
> @@ -849,52 +852,45 @@ static void __reset_control_put_internal(struct reset_control *rstc)
> kref_put(&rstc->refcnt, __reset_control_release);
> }
>
> -static int __reset_add_reset_gpio_lookup(struct gpio_device *gdev, int id,
> - struct device_node *np,
> - unsigned int gpio,
> - unsigned int of_flags)
> +static void reset_aux_device_release(struct device *dev)
static void reset_gpio_aux_device_release(struct device *dev)
[...]
> @@ -903,8 +899,10 @@ static int __reset_add_reset_gpio_lookup(struct gpio_device *gdev, int id,
> static int __reset_add_reset_gpio_device(const struct of_phandle_args *args)
> {
> struct reset_gpio_lookup *rgpio_dev;
> - struct auxiliary_device *adev;
> - int id, ret;
> + struct property_entry properties[2];
It would be nice if this could be initialized instead of the memset() +
assignment below. Maybe splitting the function will make this more
convenient.
> + unsigned int offset, of_flags;
> + struct device *parent;
> + int id, ret, lflags;
Should this be unsigned int, or enum gpio_lookup_flags?
>
> /*
> * Currently only #gpio-cells=2 is supported with the meaning of:
> @@ -915,11 +913,30 @@ static int __reset_add_reset_gpio_device(const struct of_phandle_args *args)
> if (args->args_count != 2)
> return -ENOENT;
>
> + offset = args->args[0];
> + of_flags = args->args[1];
> +
> + /*
> + * Later we map GPIO flags between OF and Linux, however not all
> + * constants from include/dt-bindings/gpio/gpio.h and
> + * include/linux/gpio/machine.h match each other.
> + *
> + * FIXME: Find a better way of translating OF flags to GPIO lookup
> + * flags.
> + */
> + if (of_flags > GPIO_ACTIVE_LOW) {
> + pr_err("reset-gpio code does not support GPIO flags %u for GPIO %u\n",
> + of_flags, offset);
> + return -EINVAL;
> + }
> +
> struct gpio_device *gdev __free(gpio_device_put) =
> gpio_device_find_by_fwnode(of_fwnode_handle(args->np));
> if (!gdev)
> return -EPROBE_DEFER;
>
> + parent = gpio_device_to_device(gdev);
> +
> /*
> * Registering reset-gpio device might cause immediate
> * bind, resulting in its probe() registering new reset controller thus
> @@ -936,6 +953,13 @@ static int __reset_add_reset_gpio_device(const struct of_phandle_args *args)
> }
> }
>
> + lflags = GPIO_PERSISTENT | (of_flags & GPIO_ACTIVE_LOW);
Could we get an of_flags_to_gpio_lookup_flags() kind of helper for
this?
> +
> + memset(properties, 0, sizeof(properties));
> + properties[0] = PROPERTY_ENTRY_GPIO_FWNODE("reset-gpios",
> + parent->fwnode,
> + offset, lflags);
> +
> id = ida_alloc(&reset_gpio_ida, GFP_KERNEL);
> if (id < 0)
> return id;
regards
Philipp
next prev parent reply other threads:[~2025-10-06 15:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 13:00 [PATCH 0/9] reset: rework reset-gpios handling Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 1/9] software node: read the reference args via the fwnode API Bartosz Golaszewski
2025-10-13 20:05 ` Andy Shevchenko
2025-10-22 7:51 ` Bartosz Golaszewski
2025-10-22 8:24 ` Sakari Ailus
2025-10-22 8:35 ` Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 2/9] software node: increase the reference of the swnode by its fwnode Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 3/9] software node: allow referencing firmware nodes Bartosz Golaszewski
2025-10-13 20:11 ` Andy Shevchenko
2025-10-20 8:06 ` Bartosz Golaszewski
2025-10-20 10:05 ` Andy Shevchenko
2025-10-20 11:26 ` Bartosz Golaszewski
2025-10-21 6:54 ` Sakari Ailus
2025-10-21 9:06 ` Bartosz Golaszewski
2025-10-21 9:14 ` Andy Shevchenko
2025-10-06 13:00 ` [PATCH 4/9] gpio: swnode: don't use the swnode's name as the key for GPIO lookup Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 5/9] gpio: swnode: update the property definitions Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 6/9] reset: order includes alphabetically in reset/core.c Bartosz Golaszewski
2025-10-06 15:20 ` Philipp Zabel
2025-10-06 13:00 ` [PATCH 7/9] reset: make the provider of reset-gpios the parent of the reset device Bartosz Golaszewski
2025-10-06 15:19 ` Philipp Zabel
2025-10-20 15:25 ` Bartosz Golaszewski
2025-10-21 9:17 ` Philipp Zabel
2025-10-21 9:27 ` Bartosz Golaszewski
2025-10-21 9:31 ` Philipp Zabel
2025-10-21 9:39 ` Bartosz Golaszewski
2025-10-21 14:55 ` Andy Shevchenko
2025-10-21 15:03 ` Andy Shevchenko
2025-10-21 15:23 ` Bartosz Golaszewski
2025-10-21 15:47 ` Andy Shevchenko
2025-10-22 8:39 ` Philipp Zabel
2025-10-22 12:17 ` Bartosz Golaszewski
2025-10-22 16:11 ` Andy Shevchenko
2025-10-20 15:56 ` Bartosz Golaszewski
2025-10-06 13:00 ` [PATCH 8/9] reset: gpio: convert the driver to using the auxiliary bus Bartosz Golaszewski
2025-10-06 15:22 ` Philipp Zabel
2025-10-06 13:00 ` [PATCH 9/9] reset: gpio: use software nodes to setup the GPIO lookup Bartosz Golaszewski
2025-10-06 15:55 ` Philipp Zabel [this message]
2025-10-10 14:07 ` Bartosz Golaszewski
2025-10-17 7:12 ` [PATCH 0/9] reset: rework reset-gpios handling Bartosz Golaszewski
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=e6a120d4ada6d032f69812f14a7e794ac1796a85.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).