From: Geert Uytterhoeven <geert@linux-m68k.org> To: Randy Dunlap <rdunlap@infradead.org> Cc: Linus Walleij <linus.walleij@linaro.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, Jonathan Corbet <corbet@lwn.net>, Harish Jenny K N <harish_kandiga@mentor.com>, Eugeniu Rosca <erosca@de.adit-jv.com>, Alexander Graf <graf@amazon.com>, Peter Maydell <peter.maydell@linaro.org>, Paolo Bonzini <pbonzini@redhat.com>, Phil Reid <preid@electromag.com.au>, Marc Zyngier <marc.zyngier@arm.com>, Christoffer Dall <christoffer.dall@arm.com>, Magnus Damm <magnus.damm@gmail.com>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>, "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, QEMU Developers <qemu-devel@nongnu.org> Subject: Re: [PATCH v5 4/5] docs: gpio: Add GPIO Aggregator documentation Date: Tue, 18 Feb 2020 20:09:12 +0100 [thread overview] Message-ID: <CAMuHMdU9=vgO6ohoYTQMGjoFzhRy=4hYGjVyRsTK2uoNsU08XQ@mail.gmail.com> (raw) In-Reply-To: <e2530fff-a17c-ae90-ba92-360b828582da@infradead.org> 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
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Randy Dunlap <rdunlap@infradead.org> Cc: Mark Rutland <mark.rutland@arm.com>, Peter Maydell <peter.maydell@linaro.org>, QEMU Developers <qemu-devel@nongnu.org>, Phil Reid <preid@electromag.com.au>, Jonathan Corbet <corbet@lwn.net>, Marc Zyngier <marc.zyngier@arm.com>, Linus Walleij <linus.walleij@linaro.org>, "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>, Magnus Damm <magnus.damm@gmail.com>, Christoffer Dall <christoffer.dall@arm.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, Rob Herring <robh+dt@kernel.org>, Harish Jenny K N <harish_kandiga@mentor.com>, "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>, Alexander Graf <graf@amazon.com>, Eugeniu Rosca <erosca@de.adit-jv.com> Subject: Re: [PATCH v5 4/5] docs: gpio: Add GPIO Aggregator documentation Date: Tue, 18 Feb 2020 20:09:12 +0100 [thread overview] Message-ID: <CAMuHMdU9=vgO6ohoYTQMGjoFzhRy=4hYGjVyRsTK2uoNsU08XQ@mail.gmail.com> (raw) In-Reply-To: <e2530fff-a17c-ae90-ba92-360b828582da@infradead.org> 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
next prev parent reply other threads:[~2020-02-18 19:09 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-18 15:18 [PATCH v5 0/5] gpio: Add GPIO Aggregator Geert Uytterhoeven 2020-02-18 15:18 ` Geert Uytterhoeven 2020-02-18 15:18 ` [PATCH v5 1/5] gpiolib: Add support for gpiochipN-based table lookup Geert Uytterhoeven 2020-02-18 15:18 ` Geert Uytterhoeven 2020-03-12 14:23 ` Linus Walleij 2020-03-12 14:23 ` Linus Walleij 2020-03-17 8:41 ` Geert Uytterhoeven 2020-03-17 8:41 ` Geert Uytterhoeven 2020-02-18 15:18 ` [PATCH v5 2/5] gpiolib: Add support for GPIO line " Geert Uytterhoeven 2020-02-18 15:18 ` Geert Uytterhoeven 2020-02-19 10:17 ` Geert Uytterhoeven 2020-02-19 10:17 ` Geert Uytterhoeven 2020-03-12 14:21 ` Linus Walleij 2020-03-12 14:21 ` Linus Walleij 2020-03-17 8:48 ` Geert Uytterhoeven 2020-03-17 8:48 ` Geert Uytterhoeven 2020-02-18 15:18 ` [PATCH v5 3/5] gpio: Add GPIO Aggregator Geert Uytterhoeven 2020-02-18 15:18 ` Geert Uytterhoeven 2020-03-12 14:57 ` Linus Walleij 2020-03-12 14:57 ` Linus Walleij 2020-03-17 10:50 ` Geert Uytterhoeven 2020-03-17 10:50 ` Geert Uytterhoeven 2020-03-17 11:32 ` Geert Uytterhoeven 2020-03-17 11:32 ` Geert Uytterhoeven 2020-02-18 15:18 ` [PATCH v5 4/5] docs: gpio: Add GPIO Aggregator documentation Geert Uytterhoeven 2020-02-18 15:18 ` Geert Uytterhoeven 2020-02-18 18:29 ` Randy Dunlap 2020-02-18 18:29 ` Randy Dunlap 2020-02-18 19:09 ` Geert Uytterhoeven [this message] 2020-02-18 19:09 ` Geert Uytterhoeven 2020-02-21 16:34 ` Geert Uytterhoeven 2020-02-21 16:34 ` Geert Uytterhoeven 2020-02-21 16:35 ` Randy Dunlap 2020-02-21 16:35 ` Randy Dunlap 2020-02-18 15:18 ` [PATCH v5 5/5] MAINTAINERS: Add GPIO Aggregator section Geert Uytterhoeven 2020-02-18 15:18 ` Geert Uytterhoeven 2020-02-18 17:04 ` [PATCH v5 0/5] gpio: Add GPIO Aggregator Eugeniu Rosca 2020-02-18 17:04 ` Eugeniu Rosca 2020-02-21 16:39 ` Geert Uytterhoeven 2020-02-21 16:39 ` 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='CAMuHMdU9=vgO6ohoYTQMGjoFzhRy=4hYGjVyRsTK2uoNsU08XQ@mail.gmail.com' \ --to=geert@linux-m68k.org \ --cc=bgolaszewski@baylibre.com \ --cc=christoffer.dall@arm.com \ --cc=corbet@lwn.net \ --cc=erosca@de.adit-jv.com \ --cc=graf@amazon.com \ --cc=harish_kandiga@mentor.com \ --cc=linus.walleij@linaro.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=magnus.damm@gmail.com \ --cc=marc.zyngier@arm.com \ --cc=mark.rutland@arm.com \ --cc=pbonzini@redhat.com \ --cc=peter.maydell@linaro.org \ --cc=preid@electromag.com.au \ --cc=qemu-devel@nongnu.org \ --cc=rdunlap@infradead.org \ --cc=robh+dt@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.