From: Johan Hovold <johan@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Kent Gibson <warthog618@gmail.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 1/1] gpiolib: Introduce for_each_gpio_desc_if() macro
Date: Thu, 20 May 2021 10:07:03 +0200 [thread overview]
Message-ID: <YKYYp6Z4HAYHLaFz@hovoldconsulting.com> (raw)
In-Reply-To: <20210518083339.23416-1-andriy.shevchenko@linux.intel.com>
On Tue, May 18, 2021 at 11:33:39AM +0300, Andy Shevchenko wrote:
> In a few places we are using a loop against all GPIO descriptors
> with a given flag for a given device. Replace it with a consolidated
> for_each type of macro.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v2: fixed compilation issue (LKP), injected if (test_bit) into the loop
> drivers/gpio/gpiolib-of.c | 10 ++++------
> drivers/gpio/gpiolib-sysfs.c | 7 ++-----
> drivers/gpio/gpiolib.c | 7 +++----
> drivers/gpio/gpiolib.h | 7 +++++++
> 4 files changed, 16 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c
> index bbcc7c073f63..2f8f3f0c8373 100644
> --- a/drivers/gpio/gpiolib-of.c
> +++ b/drivers/gpio/gpiolib-of.c
> @@ -711,14 +711,12 @@ static int of_gpiochip_scan_gpios(struct gpio_chip *chip)
> static void of_gpiochip_remove_hog(struct gpio_chip *chip,
> struct device_node *hog)
> {
> - struct gpio_desc *descs = chip->gpiodev->descs;
> + struct gpio_desc *desc;
> unsigned int i;
>
> - for (i = 0; i < chip->ngpio; i++) {
> - if (test_bit(FLAG_IS_HOGGED, &descs[i].flags) &&
> - descs[i].hog == hog)
> - gpiochip_free_own_desc(&descs[i]);
> - }
> + for_each_gpio_desc_if(i, chip, desc, FLAG_IS_HOGGED)
> + if (desc->hog == hog)
> + gpiochip_free_own_desc(desc);
The _if suffix here is too vague.
Please use a more descriptive name so that you don't need to look at the
implementation to understand what the macro does.
Perhaps call it
for_each_gpio_desc_with_flag()
or just add the more generic macro
for_each_gpio_desc()
and open-code the test so that it's clear what's going on here.
> struct gpio_desc *gpiochip_get_desc(struct gpio_chip *gc, unsigned int hwnum);
> +
> +#define for_each_gpio_desc_if(i, gc, desc, flag) \
> + for (i = 0, desc = gpiochip_get_desc(gc, i); \
> + i < gc->ngpio; \
> + i++, desc = gpiochip_get_desc(gc, i)) \
> + if (!test_bit(flag, &desc->flags)) {} else
> +
> int gpiod_get_array_value_complex(bool raw, bool can_sleep,
> unsigned int array_size,
> struct gpio_desc **desc_array,
Johan
next prev parent reply other threads:[~2021-05-20 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 8:33 [PATCH v2 1/1] gpiolib: Introduce for_each_gpio_desc_if() macro Andy Shevchenko
2021-05-18 23:41 ` Linus Walleij
2021-05-20 8:07 ` Johan Hovold [this message]
2021-05-20 8:15 ` Andy Shevchenko
2021-05-20 8:33 ` Johan Hovold
2021-05-20 9:03 ` Andy Shevchenko
2021-05-20 9:07 ` Andy Shevchenko
2021-05-20 9:16 ` Andy Shevchenko
2021-05-20 9:41 ` Johan Hovold
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=YKYYp6Z4HAYHLaFz@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@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