From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] gpiolib: Return label, if set, for IRQ only line
Date: Thu, 9 May 2024 16:58:44 +0300 [thread overview]
Message-ID: <ZjzWlNdDVVBRD-Ma@surfacebook.localdomain> (raw)
In-Reply-To: <CAMRc=Me3XOy6HfqjxDQBwnSW9pOCtK_Ry7keJ2LiXGFB88t4nA@mail.gmail.com>
Thu, May 09, 2024 at 03:15:05PM +0200, Bartosz Golaszewski kirjoitti:
> On Wed, May 8, 2024 at 4:47 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > If line has been locked as IRQ without requesting,
> > still check its label and return it, if not NULL.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > drivers/gpio/gpiolib.c | 12 ++++++------
> > 1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index db536ec9734d..1f1673552767 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -105,16 +105,16 @@ const char *gpiod_get_label(struct gpio_desc *desc)
> > unsigned long flags;
> >
> > flags = READ_ONCE(desc->flags);
> > - if (test_bit(FLAG_USED_AS_IRQ, &flags) &&
> > - !test_bit(FLAG_REQUESTED, &flags))
> > - return "interrupt";
> > -
> > - if (!test_bit(FLAG_REQUESTED, &flags))
> > - return NULL;
> >
> > label = srcu_dereference_check(desc->label, &desc->srcu,
> > srcu_read_lock_held(&desc->srcu));
> >
> > + if (test_bit(FLAG_USED_AS_IRQ, &flags))
> > + return label->str ?: "interrupt";
> > +
> > + if (!test_bit(FLAG_REQUESTED, &flags))
> > + return NULL;
> > +
> > return label->str;
> > }
>
> What good would it be if gpiochip_dup_line_label() returns NULL for
> unrequested lines anyway?
Then it should be handled differently in those cases. So, consider it as
a preparatory patch which doesn't change current behaviour.
(Yes, I have some hack patches locally which do something useful, but they are
not ready. In any case this one looks to me as a good cleanup on its own for
the sake of readability of the code and reduced amount of checks.)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-09 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 14:47 [PATCH v1 1/1] gpiolib: Return label, if set, for IRQ only line Andy Shevchenko
2024-05-09 13:15 ` Bartosz Golaszewski
2024-05-09 13:58 ` Andy Shevchenko [this message]
2024-05-09 14:23 ` Bartosz Golaszewski
2024-05-10 15:42 ` Andy Shevchenko
2024-05-10 15:48 ` Andy Shevchenko
2024-05-10 16:06 ` Andy Shevchenko
2024-05-10 17:30 ` Bartosz Golaszewski
2024-05-10 17:47 ` Andy Shevchenko
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=ZjzWlNdDVVBRD-Ma@surfacebook.localdomain \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox