Received-SPF: pass (google.com: domain of linux-kernel+bounces-169692-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Precedence: bulk
MIME-Version: 1.0
References: <20240505141420.627398-1-andy.shevchenko@gmail.com>
 <CACRpkdap=KXuyoCjWt_v53ArRPynDQndAjjHfvapLUM7VWbbdA@mail.gmail.com> <CAHp75Vdn+F=MMAyguOFup5xyOCEVZowOordiEG1FQ9Y22kLdDg@mail.gmail.com>
In-Reply-To: <CAHp75Vdn+F=MMAyguOFup5xyOCEVZowOordiEG1FQ9Y22kLdDg@mail.gmail.com>
From: Andy Shevchenko <andy.shevchenko@gmail.com>
Date: Mon, 6 May 2024 13:44:26 +0300
Message-ID: <CAHp75Vey_gJ9KHemwK4QdStdW4vYCTWnY2yUwNxWycaZg3SgUQ@mail.gmail.com>
Subject: Re: [PATCH v1 1/1] gpiolib: Discourage to use formatting strings in
 line names
To: Linus Walleij <linus.walleij@linaro.org>, Kent Gibson <warthog618@gmail.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>, linux-gpio@vger.kernel.org, 
	linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>, 
	=?UTF-8?B?TWFyZWsgQmVow7pu?= <kabel@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, May 6, 2024 at 1:39=E2=80=AFPM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> On Mon, May 6, 2024 at 10:19=E2=80=AFAM Linus Walleij <linus.walleij@lina=
ro.org> wrote:
> > On Sun, May 5, 2024 at 4:14=E2=80=AFPM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> >
> > > Currently the documentation for line names allows to use %u inside
> > > the alternative name. This is broken in character device approach
> > > from day 1 and being in use solely in sysfs.
> > >
> > > Character device interface has a line number as a part of its address=
,
> > > so the users better rely on it. Hence remove the misleading documenta=
tion.
> > >
> > > On top of that, there are no in-kernel users (out of 6, if I'm correc=
t)
> > > for such names and moreover if one exists it won't help in distinguis=
hing
> > > lines with the same naming as '%u' will also be in them and we will g=
et
> > > a warning in gpiochip_set_desc_names() for such cases.

Dunno if I need to elaborate this more, but just in case here is one:
Even if one puts '%u' to one line and avoids putting it into other:

 "gpio%u.foo"
 "gpioX.foo"

it means that it was already in mind to distinguish them beforehand,
diminishing the '%u' appearance in the first place. I.e. one may do

 "foo X"
 "foo Y"

to begin with. Besides that repetitive namings are discouraged and
most likely have no value but confusion.
For example,

"gpio%u.SPI CS"
"gpio%u.SPI CS"

would be rather

"SPI CS 0"
"SPI CS 1"

which is much more clearer to the user.

> > > Signed-off-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> >
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Thank you!
>
> Meanwhile, Cc'ing to Kent as well.
>
> --
> With Best Regards,
> Andy Shevchenko


--=20
With Best Regards,
Andy Shevchenko