From: Flavio Suligoi <f.suligoi@asem.it>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Johan Hovold <johan@kernel.org>
Subject: R: [PATCH v2] gpiolib: Disallow identical line names in the same chip
Date: Fri, 8 Jan 2021 14:43:23 +0000 [thread overview]
Message-ID: <4187c68a8567442f9a1ff365d28085af@asem.it> (raw)
In-Reply-To: <CAMuHMdUoWv9qZLYzQyxXsGd4mhiqA7SRHYF33EvSvjBUOzYVnw@mail.gmail.com>
Hi Geert,
> > > > about the duplicate line names, what do you think
> > > > about adding to the command "gpiofind" of libgpiod tools,
> > > > the possibility to discover all the duplicate gpio lines?
> > > >
> > > > For example, something like the following:
> > > >
> > > > # gpiofind button_1
> > > > gpiochip0 20
> > > > gpiochip0 22 (duplicate)
> > >
> > > This cannot happen, as the duplicate is on the same gpiochip.
> >
> > Just a question: I think that a duplicate name can be present
> > both in the same gpiochip and also in different gpiochips.
> > The same gpio line name can be wrongly present on different gpiochips,
> > for example caused by a mistake writing an ACPI table.
>
> A duplicate name in the same gpiochip is rejected, as per the patch that
> started this thread.
right, thanks Geert!
>
> Gr{oetje,eeting}s,
>
> Geert
Best regards,
Flavio
next prev parent reply other threads:[~2021-01-08 14:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 8:27 [PATCH v2] gpiolib: Disallow identical line names in the same chip Linus Walleij
2021-01-05 17:29 ` Andy Shevchenko
2021-01-05 23:23 ` Linus Walleij
2021-01-06 10:09 ` Bartosz Golaszewski
2021-01-06 13:34 ` Andy Shevchenko
2021-01-06 14:25 ` Bartosz Golaszewski
2021-01-06 16:14 ` Andy Shevchenko
2021-01-07 10:03 ` R: " Flavio Suligoi
2021-01-07 10:12 ` Andy Shevchenko
2021-01-07 13:12 ` R: " Flavio Suligoi
2021-01-08 10:40 ` Flavio Suligoi
2021-01-08 15:03 ` Andy Shevchenko
2021-01-07 10:45 ` Linus Walleij
2021-01-07 13:49 ` R: " Flavio Suligoi
2021-01-07 13:55 ` Geert Uytterhoeven
2021-01-08 14:39 ` R: " Flavio Suligoi
2021-01-08 14:41 ` Geert Uytterhoeven
2021-01-08 14:43 ` Flavio Suligoi [this message]
2021-01-08 15:05 ` Andy Shevchenko
2021-01-15 14:30 ` Bartosz Golaszewski
[not found] ` <CAHp75Vd017YY8HU-Ai7jnQEJ4PEgiU4VXn-jhLBKwERmsG_5MA@mail.gmail.com>
2021-01-15 17:31 ` Geert Uytterhoeven
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=4187c68a8567442f9a1ff365d28085af@asem.it \
--to=f.suligoi@asem.it \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).