From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 10/15 v3] gpio: devres: Handle nonexclusive GPIOs
Date: Wed, 5 Dec 2018 15:34:11 +0100 [thread overview]
Message-ID: <626564ae-8dd6-d271-7a4f-11071df2d7e8@samsung.com> (raw)
In-Reply-To: <20181205124721.26624-11-linus.walleij@linaro.org>
Hi Linus,
On 2018-12-05 13:47, Linus Walleij wrote:
> When we get a nonexeclusive GPIO descriptor using managed
> resources, we should only add it to the list of managed
> resources once: on the first user. Augment the
> devm_gpiod_get_index() and devm_gpiod_get_from_of_node()
> calls to account for this by checking if the descriptor
> is already resource managed before we proceed to allocate
> a new resource management struct.
>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> Fixes: b0ce7b29bfcd ("regulator/gpio: Allow nonexclusive GPIO access")
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v3:
> - New patch.
> - This fix is in response to an issue Marek saw in the fixups
> for resource-managed GPIO descriptors used with ena_gpiod
> in the regulator subsystem.
> - I first thought to apply it to the GPIO tree directly, but
> since it is not a regression it is better to put it into
> the regulator tree with the rest of the patches.
> ---
> drivers/gpio/gpiolib-devres.c | 50 ++++++++++++++++++++++++++---------
> 1 file changed, 38 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib-devres.c b/drivers/gpio/gpiolib-devres.c
> index 01959369360b..a57e968025a8 100644
> --- a/drivers/gpio/gpiolib-devres.c
> +++ b/drivers/gpio/gpiolib-devres.c
> @@ -98,15 +98,28 @@ struct gpio_desc *__must_check devm_gpiod_get_index(struct device *dev,
> struct gpio_desc **dr;
> struct gpio_desc *desc;
>
> + desc = gpiod_get_index(dev, con_id, idx, flags);
> + if (IS_ERR(desc))
> + return desc;
> +
> + /*
> + * For non-exclusive GPIO descriptors, check if this descriptor is
> + * already under resource management by this device.
> + */
> + if (flags & GPIOD_FLAGS_BIT_NONEXCLUSIVE) {
> + struct devres *dres;
> +
> + dres = devres_find(dev, devm_gpiod_release,
> + devm_gpiod_match, desc);
devres_find(dev, devm_gpiod_release, devm_gpiod_match, &desc);
> + if (dres)
> + return desc;
> + }
> +
> dr = devres_alloc(devm_gpiod_release, sizeof(struct gpio_desc *),
> GFP_KERNEL);
> - if (!dr)
> + if (!dr) {
> + gpiod_put(desc);
> return ERR_PTR(-ENOMEM);
> -
> - desc = gpiod_get_index(dev, con_id, idx, flags);
> - if (IS_ERR(desc)) {
> - devres_free(dr);
> - return desc;
> }
>
> *dr = desc;
> @@ -140,15 +153,28 @@ struct gpio_desc *devm_gpiod_get_from_of_node(struct device *dev,
> struct gpio_desc **dr;
> struct gpio_desc *desc;
>
> + desc = gpiod_get_from_of_node(node, propname, index, dflags, label);
> + if (IS_ERR(desc))
> + return desc;
> +
> + /*
> + * For non-exclusive GPIO descriptors, check if this descriptor is
> + * already under resource management by this device.
> + */
> + if (dflags & GPIOD_FLAGS_BIT_NONEXCLUSIVE) {
> + struct devres *dres;
> +
> + dres = devres_find(dev, devm_gpiod_release,
> + devm_gpiod_match, desc);
devres_find(dev, devm_gpiod_release, devm_gpiod_match, &desc);
> + if (dres)
> + return desc;
> + }
> +
> dr = devres_alloc(devm_gpiod_release, sizeof(struct gpio_desc *),
> GFP_KERNEL);
> - if (!dr)
> + if (!dr) {
> + gpiod_put(desc);
> return ERR_PTR(-ENOMEM);
> -
> - desc = gpiod_get_from_of_node(node, propname, index, dflags, label);
> - if (IS_ERR(desc)) {
> - devres_free(dr);
> - return desc;
> }
>
> *dr = desc;
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2018-12-05 14:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 12:47 [PATCH 00/15 v3] Regulator ena_gpiod fixups Linus Walleij
2018-12-05 12:47 ` [PATCH 01/15 v3] regulator: core: Track dangling GPIO descriptors Linus Walleij
2018-12-05 12:47 ` [PATCH 02/15 v3] regulator: fixed: Let core handle GPIO descriptor Linus Walleij
2018-12-05 12:47 ` [PATCH 03/15 v3] regulator: lm363x: " Linus Walleij
2018-12-05 12:47 ` [PATCH 04/15 v3] regulator: lp8788-ldo: " Linus Walleij
2018-12-05 12:47 ` [PATCH 05/15 v3] regulator: max8952: " Linus Walleij
2018-12-05 12:47 ` [PATCH 06/15 v3] regulator: max8973: " Linus Walleij
2018-12-05 13:43 ` Charles Keepax
2018-12-05 14:42 ` Linus Walleij
2018-12-05 15:33 ` Charles Keepax
2018-12-06 8:58 ` Linus Walleij
2018-12-06 10:34 ` Charles Keepax
2018-12-06 11:47 ` Linus Walleij
2018-12-06 11:53 ` Charles Keepax
2018-12-05 12:47 ` [PATCH 07/15 v3] gpio: Export gpiod_get_from_of_node() Linus Walleij
2018-12-05 12:47 ` [PATCH 08/15 v3] regulator: max77686: Let core handle GPIO descriptor Linus Walleij
2018-12-05 12:47 ` [PATCH 09/15 v3] gpio: Enable nonexclusive gpiods from DT nodes Linus Walleij
2018-12-05 12:47 ` [PATCH 10/15 v3] gpio: devres: Handle nonexclusive GPIOs Linus Walleij
2018-12-05 14:34 ` Marek Szyprowski [this message]
2018-12-05 12:47 ` [PATCH 11/15 v3] gpio: Add devm_gpiod_unhinge() Linus Walleij
2018-12-05 14:34 ` Marek Szyprowski
2018-12-05 12:47 ` [PATCH 12/15 v3] regulator: da9211: Hand over GPIO to regulator core Linus Walleij
2018-12-05 12:47 ` [PATCH 13/15 v3] regulator: s5m8767: " Linus Walleij
2018-12-05 12:47 ` [PATCH 14/15 v3] regulator: tps65090: " Linus Walleij
2018-12-05 12:47 ` [PATCH 15/15 v3] regulator: s2mps11: " 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=626564ae-8dd6-d271-7a4f-11071df2d7e8@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.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
all inboxes | Powered by JetHome®