Re: [PATCH v2] gpiolib: Disallow identical line names in the same chip

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Flavio,

On Fri, Jan 8, 2021 at 3:39 PM Flavio Suligoi <f.suligoi@xxxxxxx> wrote:
> > > 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.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds



[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux