From: Kent Gibson <warthog618@gmail.com>
To: Sameh Mohamed <sameh4@gmx.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [libgpiod] Question regarding locks / race conditions
Date: Mon, 17 Apr 2023 22:17:06 +0800 [thread overview]
Message-ID: <ZD1U4lu12W4GKRPN@sol> (raw)
In-Reply-To: <CABrMOxbWa8mxA=ckAu6QVKnej5o7UGrWXdeDMaAqScGVVk3=wA@mail.gmail.com>
On Mon, Apr 17, 2023 at 10:13:18AM -0400, Sameh Mohamed wrote:
> Thanks Kent and Bartosz,
>
> @Kent: you are correct, I don't intend to share any line requests on the
> same line, rather I am curious what will happen if two threads create two
> requests for two lines at the same time. For instance two threads setting
> values on different GPIO pins but at the same time.
>
No locks necessary - the kernel will deal with any resource contention
internally.
Cheers,
Kent.
prev parent reply other threads:[~2023-04-17 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABrMOxZY6Q3wiYsJUaXZiSET_gjMJ3GWaMrDCXwXC6nf7AX2_g@mail.gmail.com>
2023-04-17 7:19 ` [libgpiod] Question regarding locks / race conditions Bartosz Golaszewski
2023-04-17 12:29 ` Kent Gibson
[not found] ` <CABrMOxbWa8mxA=ckAu6QVKnej5o7UGrWXdeDMaAqScGVVk3=wA@mail.gmail.com>
2023-04-17 14:17 ` Kent Gibson [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=ZD1U4lu12W4GKRPN@sol \
--to=warthog618@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sameh4@gmx.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).