linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Flavio Suligoi <f.suligoi@asem.it>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Johan Hovold <johan@kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: R: [PATCH v2] gpiolib: Disallow identical line names in the same chip
Date: Fri, 8 Jan 2021 10:40:14 +0000	[thread overview]
Message-ID: <4a7c2f63ec2c4cde9742603e3cbbaee8@asem.it> (raw)
In-Reply-To: <CAHp75VcVN5Af3t-OYdO9MOXk14LV+zYQtusqft8twi_u83yZ6g@mail.gmail.com>

Hi Andy,
 
> Flavio, perhaps one more rule to the gpio-line-names property has to
> be added into documentation (Bart, same to DT docs?):
>  - names inside one chip must be unique
 
Just a question: why "inside one chip" only?
The name should be unique for all gpiochips, since "gpiofind"
stops at the first name match, and doesn't show other gpios
names, even if they exist, with the same name, in other gpiochip.

I think that a rule as:

- names must be unique (avoid duplicates in any gpiochips) 

> --
> With Best Regards,
> Andy Shevchenko

Best regards,
Flavio Suligoi

  parent reply	other threads:[~2021-01-08 10:40 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 [this message]
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                 ` R: " Flavio Suligoi
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=4a7c2f63ec2c4cde9742603e3cbbaee8@asem.it \
    --to=f.suligoi@asem.it \
    --cc=andy.shevchenko@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=geert+renesas@glider.be \
    --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).