Messages in this thread | | | From | Geert Uytterhoeven <> | Date | Tue, 18 Feb 2020 20:09:12 +0100 | Subject | Re: [PATCH v5 4/5] docs: gpio: Add GPIO Aggregator documentation |
| |
Hi Randy,
On Tue, Feb 18, 2020 at 7:30 PM Randy Dunlap <rdunlap@infradead.org> wrote: > On 2/18/20 7:18 AM, Geert Uytterhoeven wrote: > > Document the GPIO Aggregator, and the two typical use-cases. > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > --- /dev/null > > +++ b/Documentation/admin-guide/gpio/gpio-aggregator.rst > > @@ -0,0 +1,102 @@ > > +.. SPDX-License-Identifier: GPL-2.0-only > > + > > +GPIO Aggregator > > +=============== > > + > > +The GPIO Aggregator allows to aggregate GPIOs, and expose them as a new > > "allows" really wants an object following the verb [although the kernel sources > and docs have many cases of it not having an object]. Something like > > allows {you, one, someone, users, a user} to aggregate
Thanks for the hint!
> > + Example: Instantiate a new GPIO aggregator by aggregating GPIO > > + 19 of "e6052000.gpio" and GPIOs 20-21 of "gpiochip2" into a new > > + gpio_chip: > > + > > + .. code-block:: bash > > + > > + echo 'e6052000.gpio 19 gpiochip2 20-21' > new_device > > + > > Does the above command tell the user that the new device is named > "gpio-aggregator.0", as used below?
Yes, it will be printed through the kernel log, cfr. the sample session in the cover letter.
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
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
| |