linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Vincent Pelletier <plr.vincent@gmail.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: gpiochip_lock_as_irq on pins without FLAG_REQUESTED: bug or feature ?
Date: Fri, 2 Jul 2021 23:46:16 +0200	[thread overview]
Message-ID: <CACRpkdbnujCU1H6VmpyZ7p6bMFG0s8PzT-O4GetLUXA21N63qg@mail.gmail.com> (raw)
In-Reply-To: <20210702104810.581438d0@gmail.com>

On Fri, Jul 2, 2021 at 12:48 PM Vincent Pelletier <plr.vincent@gmail.com> wrote:

> gpiochip_lock_as_irq,
(...)
> Actually my question came from yet another misunderstanding on my side:
> I expected this function to act as an exclusive access control (because
> of the "lock" in the name), but I then realised my assumption is wrong.

Well it locks its use to be compliant with being used for IRQ.
So it cannot be turned into an output for example. While reading
its value as input is fine.

Yours,
Linus Walleij

      reply	other threads:[~2021-07-02 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28  3:36 gpiochip_lock_as_irq on pins without FLAG_REQUESTED: bug or feature ? Vincent Pelletier
2021-06-28 13:40 ` Andy Shevchenko
2021-06-28 13:42   ` Andy Shevchenko
2021-06-28 22:52     ` Vincent Pelletier
2021-06-29 10:19       ` Andy Shevchenko
2021-07-01 13:36         ` Vincent Pelletier
2021-07-02  0:24       ` Linus Walleij
2021-07-02  0:09 ` Linus Walleij
2021-07-02 10:48   ` Vincent Pelletier
2021-07-02 21:46     ` Linus Walleij [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=CACRpkdbnujCU1H6VmpyZ7p6bMFG0s8PzT-O4GetLUXA21N63qg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plr.vincent@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).