linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH v3 09/10] gpiolib: use gpiochip_dup_line_label() in for_each helpers
Date: Mon,  4 Dec 2023 10:35:08 +0100	[thread overview]
Message-ID: <20231204093509.19225-10-brgl@bgdev.pl> (raw)
In-Reply-To: <20231204093509.19225-1-brgl@bgdev.pl>

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Rework for_each_requested_gpio_in_range() to use the new helper to
retrieve a dynamically allocated copy of the descriptor label and free
it at the end of each iteration. We need to leverage the CLASS()'
destructor to make sure that the label is freed even when breaking out
of the loop.

Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
 include/linux/gpio/driver.h | 37 +++++++++++++++++++++++++++++--------
 1 file changed, 29 insertions(+), 8 deletions(-)

diff --git a/include/linux/gpio/driver.h b/include/linux/gpio/driver.h
index 9796a34e2fee..910fc50d3ab5 100644
--- a/include/linux/gpio/driver.h
+++ b/include/linux/gpio/driver.h
@@ -534,17 +534,38 @@ struct gpio_chip {
 const char *gpiochip_is_requested(struct gpio_chip *gc, unsigned int offset);
 char *gpiochip_dup_line_label(struct gpio_chip *gc, unsigned int offset);
 
+
+struct _gpiochip_for_each_data {
+	const char **label;
+	unsigned int *i;
+};
+
+DEFINE_CLASS(_gpiochip_for_each_data,
+	     struct _gpiochip_for_each_data,
+	     if (*_T.label) kfree(*_T.label),
+	     ({
+		struct _gpiochip_for_each_data _data = { label, i };
+		*_data.i = 0;
+		_data;
+	     }),
+	     const char **label, int *i)
+
 /**
  * for_each_requested_gpio_in_range - iterates over requested GPIOs in a given range
- * @chip:	the chip to query
- * @i:		loop variable
- * @base:	first GPIO in the range
- * @size:	amount of GPIOs to check starting from @base
- * @label:	label of current GPIO
+ * @_chip:	the chip to query
+ * @_i:		loop variable
+ * @_base:	first GPIO in the range
+ * @_size:	amount of GPIOs to check starting from @base
+ * @_label:	label of current GPIO
  */
-#define for_each_requested_gpio_in_range(chip, i, base, size, label)			\
-	for (i = 0; i < size; i++)							\
-		if ((label = gpiochip_is_requested(chip, base + i)) == NULL) {} else
+#define for_each_requested_gpio_in_range(_chip, _i, _base, _size, _label)		\
+	for (CLASS(_gpiochip_for_each_data, _data)(&_label, &_i);			\
+	     *_data.i < _size;								\
+	     (*_data.i)++, kfree(*(_data.label)), *_data.label = NULL)			\
+		if ((*_data.label =							\
+			gpiochip_dup_line_label(_chip, _base + *_data.i)) == NULL) {}	\
+		else if (IS_ERR(*_data.label)) {}					\
+		else
 
 /* Iterates over all requested GPIO of the given @chip */
 #define for_each_requested_gpio(chip, i, label)						\
-- 
2.40.1


  parent reply	other threads:[~2023-12-04  9:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  9:34 [PATCH v3 00/10] gpio/pinctrl: replace gpiochip_is_requested() with a safer interface Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 01/10] gpiolib: provide gpiochip_dup_line_label() Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 02/10] gpio: wm831x: use gpiochip_dup_line_label() Bartosz Golaszewski
2023-12-04 13:16   ` Andy Shevchenko
2023-12-04 13:38     ` Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 03/10] gpio: wm8994: " Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 04/10] gpio: stmpe: " Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 05/10] pinctrl: abx500: " Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 06/10] pinctrl: nomadik: " Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 07/10] pinctrl: baytrail: " Bartosz Golaszewski
2023-12-04 13:18   ` Andy Shevchenko
2023-12-04 13:38     ` Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 08/10] pinctrl: sppctl: " Bartosz Golaszewski
2023-12-04  9:35 ` Bartosz Golaszewski [this message]
2023-12-04 13:24   ` [PATCH v3 09/10] gpiolib: use gpiochip_dup_line_label() in for_each helpers Andy Shevchenko
2023-12-04 13:39     ` Bartosz Golaszewski
2023-12-04  9:35 ` [PATCH v3 10/10] gpiolib: remove gpiochip_is_requested() Bartosz Golaszewski
2023-12-04 13:22   ` Andy Shevchenko
2023-12-05 22:49 ` [PATCH v3 00/10] gpio/pinctrl: replace gpiochip_is_requested() with a safer interface 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=20231204093509.19225-10-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --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 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).