From: Kent Gibson <warthog618@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2] gpiolib: cdev: document that line eflags are shared
Date: Sat, 17 Oct 2020 07:39:13 +0800 [thread overview]
Message-ID: <20201016233913.GB5143@sol> (raw)
In-Reply-To: <CAHp75Ve7TspiCredTu48AwstS4YUnfKTHzvuxvhq_-c9697igg@mail.gmail.com>
On Fri, Oct 16, 2020 at 05:24:14PM +0300, Andy Shevchenko wrote:
> On Wed, Oct 14, 2020 at 12:21 PM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > The line.eflags field is shared so document this fact and highlight it
> > throughout using READ_ONCE() and WRITE_ONCE() accessors.
> >
> > Also use a local copy of the eflags in edge_irq_thread() to ensure
> > consistent control flow even if eflags changes. This is only a defensive
> > measure as edge_irq_thread() is currently disabled when the eflags are
> > changed.
>
> > - if (line->eflags == (GPIO_V2_LINE_FLAG_EDGE_RISING |
> > - GPIO_V2_LINE_FLAG_EDGE_FALLING)) {
> > + eflags = READ_ONCE(line->eflags);
> > + if (eflags == (GPIO_V2_LINE_FLAG_EDGE_RISING |
> > + GPIO_V2_LINE_FLAG_EDGE_FALLING)) {
>
> Hmm... side note: perhaps at some point
>
> #define GPIO_V2_LINE_FLAG_EDGE_BOTH \
> (GPIO_V2_LINE_FLAG_EDGE_RISING | GPIO_V2_LINE_FLAG_EDGE_FALLING)
>
> if (eflags == GPIO_V2_LINE_FLAG_EDGE_BOTH) {
>
> ?
Yeah, that would make sense. I think I used GPIO_V2_LINE_EDGE_FLAGS,
which is defined the same as your GPIO_V2_LINE_FLAG_EDGE_BOTH, here at
some point, but that just looked wrong.
The GPIO_V2_LINE_FLAG_EDGE_BOTH does read better. I'll add it to the
todo list.
Cheers,
Kent.
next prev parent reply other threads:[~2020-10-16 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 6:29 [PATCH v2] gpiolib: cdev: document that line eflags are shared Kent Gibson
2020-10-16 14:24 ` Andy Shevchenko
2020-10-16 23:39 ` Kent Gibson [this message]
2020-10-26 14:26 ` 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=20201016233913.GB5143@sol \
--to=warthog618@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.