From: Jon Hunter <jonathanh@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] gpio/regulator: Allow nonexclusive GPIO access
Date: Fri, 12 Oct 2018 11:30:34 +0100 [thread overview]
Message-ID: <0a8efd69-48da-5031-6488-c0d9fdc07a03@nvidia.com> (raw)
In-Reply-To: <20181011143531.7195-1-linus.walleij@linaro.org>
Hi Linus,
On 11/10/18 15:35, Linus Walleij wrote:
> This allows nonexclusive (simultaneous) access to a single
> GPIO line for the fixed regulator enable line. This happens
> when several regulators use the same GPIO for enabling and
> disabling a regulator, and all need a handle on their GPIO
> descriptor.
>
> This solution with a special flag is not entirely elegant
> and should ideally be replaced by something more careful as
> this makes it possible for several consumers to
> enable/disable the same GPIO line to the left and right
> without any consistency. The current use inside the regulator
> core should however be fine as it takes special care to
> handle this.
>
> For the state of the GPIO backend, this is still the
> lesser evil compared to going back to global GPIO
> numbers.
>
> Fixes: efdfeb079cc3 ("regulator: fixed: Convert to use GPIO descriptor only")
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This also fixes a regression I was seeing on Tegra124 Jetson TK1. So ...
Tested-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Hi Marek, it would be great if you could try this on top
> of linux-next and report if it solves your problem on the
> Samsung Exynos.
>
> If it does I hope it will apply cleanly on the regulator
> tree.
> ---
> drivers/gpio/gpiolib.c | 19 +++++++++++++++++--
> drivers/regulator/fixed.c | 13 +++++++++++++
> include/linux/gpio/consumer.h | 1 +
> 3 files changed, 31 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> index 7c222df8f834..f82a741ff428 100644
> --- a/drivers/gpio/gpiolib.c
> +++ b/drivers/gpio/gpiolib.c
> @@ -4144,8 +4144,23 @@ struct gpio_desc *__must_check gpiod_get_index(struct device *dev,
> * the device name as label
> */
> status = gpiod_request(desc, con_id ? con_id : devname);
> - if (status < 0)
> - return ERR_PTR(status);
> + if (status < 0) {
> + if (status == -EBUSY && flags & GPIOD_FLAGS_BIT_NONEXCLUSIVE) {
> + /*
> + * This happens when there are several consumers for
> + * the same GPIO line: we just return here without
> + * further initialization. It is a bit if a hack.
> + * This is necessary to support fixed regulators.
> + *
> + * FIXME: Make this more sane and safe.
> + */
> + dev_info(dev, "nonexclusive access to GPIO for %s\n",
> + con_id);
Nit-pick, for me the 'con_id' is NULL so should we use the same ternary
operator here as above to print devname instead in this case?
Cheers!
Jon
--
nvpublic
prev parent reply other threads:[~2018-10-12 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181011143542epcas1p24f7b9193acf33746a2fc166bf63a8f77@epcas1p2.samsung.com>
2018-10-11 14:35 ` Linus Walleij
2018-10-11 14:43 ` Mark Brown
2018-10-11 17:01 ` Linus Walleij
2018-10-11 17:54 ` Mark Brown
2018-10-11 18:41 ` Linus Walleij
2018-10-12 16:10 ` Mark Brown
2018-10-11 15:15 ` Marek Szyprowski
2018-10-12 10:30 ` Jon Hunter [this message]
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=0a8efd69-48da-5031-6488-c0d9fdc07a03@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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
all inboxes | Powered by JetHome®