From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH 3/7] gpio: exar: switch to a simpler IDA interface
Date: Mon, 26 Oct 2020 15:18:35 +0100 [thread overview]
Message-ID: <20201026141839.28536-4-brgl@bgdev.pl> (raw)
In-Reply-To: <20201026141839.28536-1-brgl@bgdev.pl>
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
We don't need to specify any ranges when allocating IDs so we can switch
to ida_alloc() and ida_free() instead of the ida_simple_ counterparts.
ida_simple_get(ida, 0, 0, gfp) is equivalent to
ida_alloc_range(ida, 0, UINT_MAX, gfp) which is equivalent to
ida_alloc(ida, gfp). Note: IDR will never actually allocate an ID
larger than INT_MAX.
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
---
drivers/gpio/gpio-exar.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-exar.c b/drivers/gpio/gpio-exar.c
index 1941ae533418..752e8437ff80 100644
--- a/drivers/gpio/gpio-exar.c
+++ b/drivers/gpio/gpio-exar.c
@@ -149,7 +149,7 @@ static int gpio_exar_probe(struct platform_device *pdev)
mutex_init(&exar_gpio->lock);
- index = ida_simple_get(&ida_index, 0, 0, GFP_KERNEL);
+ index = ida_alloc(&ida_index, GFP_KERNEL);
if (index < 0) {
ret = index;
goto err_mutex_destroy;
@@ -179,7 +179,7 @@ static int gpio_exar_probe(struct platform_device *pdev)
return 0;
err_destroy:
- ida_simple_remove(&ida_index, index);
+ ida_free(&ida_index, index);
err_mutex_destroy:
mutex_destroy(&exar_gpio->lock);
return ret;
@@ -189,7 +189,7 @@ static int gpio_exar_remove(struct platform_device *pdev)
{
struct exar_gpio_chip *exar_gpio = platform_get_drvdata(pdev);
- ida_simple_remove(&ida_index, exar_gpio->index);
+ ida_free(&ida_index, exar_gpio->index);
mutex_destroy(&exar_gpio->lock);
return 0;
--
2.29.1
next prev parent reply other threads:[~2020-10-26 14:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 14:18 [PATCH 0/7] gpio: exar: refactor the driver Bartosz Golaszewski
2020-10-26 14:18 ` [PATCH 1/7] gpio: exar: add a newline after the copyright notice Bartosz Golaszewski
2020-10-26 14:18 ` [PATCH 2/7] gpio: exar: include idr.h Bartosz Golaszewski
2020-10-26 14:18 ` Bartosz Golaszewski [this message]
2020-10-26 14:18 ` [PATCH 4/7] gpio: exar: use a helper variable for &pdev->dev Bartosz Golaszewski
2020-10-26 14:18 ` [RFT PATCH 5/7] gpio: exar: unduplicate address and offset computation Bartosz Golaszewski
2020-10-26 14:52 ` Andy Shevchenko
2020-11-02 10:16 ` Bartosz Golaszewski
2020-11-02 10:58 ` Andy Shevchenko
2020-11-02 11:27 ` David Laight
2020-10-26 14:18 ` [RFT PATCH 6/7] gpio: exar: switch to using regmap Bartosz Golaszewski
2020-10-26 14:59 ` Andy Shevchenko
2020-11-04 16:32 ` Bartosz Golaszewski
2020-10-26 14:18 ` [PATCH 7/7] gpio: exar: use devm action for freeing the IDA and drop remove() Bartosz Golaszewski
2020-10-26 15:03 ` Andy Shevchenko
2020-10-26 15:12 ` Bartosz Golaszewski
2020-10-26 14:46 ` [PATCH 0/7] gpio: exar: refactor the driver Andy Shevchenko
2020-10-26 15:05 ` Andy Shevchenko
2020-10-27 15:12 ` Jan Kiszka
2020-11-04 13:57 ` Jan Kiszka
2020-11-04 14:52 ` Andy Shevchenko
2020-11-04 16:23 ` 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=20201026141839.28536-4-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).