From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Koichiro Den <koichiro.den@canonical.com>
Cc: linux-gpio@vger.kernel.org, brgl@bgdev.pl,
linus.walleij@linaro.org, maciej.borzecki@canonical.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 04/10] gpio: aggregator: add read-write 'name' attribute
Date: Wed, 12 Feb 2025 15:27:50 +0100 [thread overview]
Message-ID: <CAMuHMdXnST1Y3oxEz_r59urauZ42nrtL5P4+rnPEsgiKgENOOg@mail.gmail.com> (raw)
In-Reply-To: <20250203031213.399914-5-koichiro.den@canonical.com>
Hi Den,
On Mon, 3 Feb 2025 at 04:12, Koichiro Den <koichiro.den@canonical.com> wrote:
> Previously, there is no way to assign names to GPIO lines exported
> through an aggregator.
>
> Allow users to set custom line names via a 'name' attribute.
>
> Signed-off-by: Koichiro Den <koichiro.den@canonical.com>
Thanks for your patch!
> --- a/drivers/gpio/gpio-aggregator.c
> +++ b/drivers/gpio/gpio-aggregator.c
> @@ -63,6 +63,8 @@ struct gpio_aggregator_line {
> /* Line index within the aggregator device */
> int idx;
>
> + /* Custom name for the virtual line */
> + char *name;
This can be const.
> /* GPIO chip label or line name */
> char *key;
Actually this can be const, too.
> /* Can be negative to indicate lookup by line name */
> @@ -678,6 +680,44 @@ gpio_aggr_line_key_store(struct config_item *item, const char *page,
>
> CONFIGFS_ATTR(gpio_aggr_line_, key);
>
> +static ssize_t
> +gpio_aggr_line_name_show(struct config_item *item, char *page)
> +{
> + struct gpio_aggregator_line *line = to_gpio_aggregator_line(item);
> + struct gpio_aggregator *aggr = line->parent;
> +
> + guard(mutex)(&aggr->lock);
> +
> + return sprintf(page, "%s\n", line->name ?: "");
sysfs_emit()
> +}
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:[~2025-02-12 14:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 3:12 [PATCH v2 00/10] Introduce configfs-based interface for gpio-aggregator Koichiro Den
2025-02-03 3:12 ` [PATCH v2 01/10] gpio: aggregator: reorder functions to prepare for configfs introduction Koichiro Den
2025-02-11 15:48 ` Geert Uytterhoeven
2025-02-03 3:12 ` [PATCH v2 02/10] gpio: aggregator: introduce basic configfs interface Koichiro Den
2025-02-04 12:48 ` Bartosz Golaszewski
2025-02-04 14:41 ` Koichiro Den
2025-02-05 13:39 ` Koichiro Den
2025-02-12 13:48 ` Geert Uytterhoeven
2025-02-13 14:12 ` Koichiro Den
2025-02-13 14:31 ` Geert Uytterhoeven
2025-02-03 3:12 ` [PATCH v2 03/10] gpio: aggregator: add read-only 'dev_name' configfs attribute Koichiro Den
2025-02-04 12:49 ` Bartosz Golaszewski
2025-02-04 14:44 ` Koichiro Den
2025-02-12 14:20 ` Geert Uytterhoeven
2025-02-13 14:13 ` Koichiro Den
2025-02-03 3:12 ` [PATCH v2 04/10] gpio: aggregator: add read-write 'name' attribute Koichiro Den
2025-02-12 14:27 ` Geert Uytterhoeven [this message]
2025-02-13 14:13 ` Koichiro Den
2025-02-03 3:12 ` [PATCH v2 05/10] gpio: aggregator: expose custom line names to forwarder gpio_chip Koichiro Den
2025-02-12 14:44 ` Geert Uytterhoeven
2025-02-13 14:13 ` Koichiro Den
2025-02-03 3:12 ` [PATCH v2 06/10] gpio: aggregator: rename 'name' to 'key' in aggr_parse() Koichiro Den
2025-02-12 14:45 ` Geert Uytterhoeven
2025-02-03 3:12 ` [PATCH v2 07/10] gpio: aggregator: clean up gpio_aggregator_free() Koichiro Den
2025-02-12 14:47 ` Geert Uytterhoeven
2025-02-03 3:12 ` [PATCH v2 08/10] gpio: aggregator: expoose aggregator created via legacy sysfs to configfs Koichiro Den
2025-02-04 13:12 ` Bartosz Golaszewski
2025-02-04 14:47 ` Koichiro Den
2025-02-12 15:36 ` Geert Uytterhoeven
2025-02-13 14:15 ` Koichiro Den
2025-02-03 3:12 ` [PATCH v2 09/10] gpio: aggregator: cancel deferred probe for devices created via configfs Koichiro Den
2025-02-04 13:14 ` Bartosz Golaszewski
2025-02-12 15:49 ` Geert Uytterhoeven
2025-02-16 13:15 ` Koichiro Den
2025-02-16 15:58 ` Bartosz Golaszewski
2025-02-17 12:52 ` Koichiro Den
2025-02-03 3:12 ` [PATCH v2 10/10] Documentation: gpio: document configfs interface for gpio-aggregator Koichiro Den
2025-02-12 15:55 ` Geert Uytterhoeven
2025-02-13 14:17 ` Koichiro Den
2025-02-12 13:14 ` [PATCH v2 00/10] Introduce configfs-based " Geert Uytterhoeven
2025-02-13 14:09 ` Koichiro Den
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=CAMuHMdXnST1Y3oxEz_r59urauZ42nrtL5P4+rnPEsgiKgENOOg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=brgl@bgdev.pl \
--cc=koichiro.den@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.borzecki@canonical.com \
/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).