From: "Jan Lübbe" <jlu@pengutronix.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Kent Gibson <warthog618@gmail.com>, Marek Vasut <marex@denx.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH RFC/RFT 00/15] gpio: sysfs: add a per-chip export/unexport attribute pair
Date: Mon, 23 Jun 2025 10:27:24 +0200 [thread overview]
Message-ID: <e3cb14a8e1a6ea1e9a050f8013730e56f79f62ec.camel@pengutronix.de> (raw)
In-Reply-To: <CAMRc=Mc6ZSp+bu3i0-X-i_8=f69X0Rez98tGsS-g_uJ1nBH6fQ@mail.gmail.com>
On Wed, 2025-06-18 at 17:56 +0200, Bartosz Golaszewski wrote:
> On Wed, Jun 18, 2025 at 3:38 PM Jan Lübbe <jlu@pengutronix.de> wrote:
> >
>
> [snip]
>
>
> > The contents of /sys/kernel/debug/gpio don't really fit any more:
> > gpiochip10: GPIOs 660-663, parent: i2c/0-0024, pca9570, can sleep:
> > gpio-660 (DUT_PWR_EN |tacd ) out hi
> > gpio-661 (DUT_PWR_DISCH |tacd ) out lo
> > gpio-662 (DUT_PWR_ADCRST |reset ) out lo
> > The header is inconsistent: it uses the 'gpiochip' prefix, but not the base as
> > the old class devices in /sys/class/gpio/. Perhaps something like this?
> > chip10: GPIOs 0-2 (global IDs 660-663), parent: i2c/0-0024, pca9570, can sleep:
> > gpio-0 (660) (DUT_PWR_EN |tacd ) out hi
> > gpio-1 (661) (DUT_PWR_DISCH |tacd ) out lo
> > gpio-2 (662) (DUT_PWR_ADCRST |reset ) out lo
> > If GPIO_SYSFS_LEGACY is disabled, the global IDs could be hidden.
> >
>
> After a second look: IMO this is unrelated to the sysfs changes. We
> definitely should change the debugfs output and rid it off the global
> numbers but it shouldn't be part of this series.
Agreed.
> Also: are you using
> this output in some way? Technically debugfs output is not stable ABI
> so we can modify it without considering existing users but wanted to
> run it by you to know if I'm going to break something for you.
We're not parsing debugfs. :) I just checked manually if it matched the new
naming and saw that it didn't.
Regards,
Jan
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-06-23 8:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 14:38 [PATCH RFC/RFT 00/15] gpio: sysfs: add a per-chip export/unexport attribute pair Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 01/15] Documentation: gpio: undocument removed behavior Bartosz Golaszewski
2025-06-11 8:15 ` Linus Walleij
2025-06-10 14:38 ` [PATCH RFC/RFT 02/15] Documentation: gpio: document the active_low field in the sysfs ABI Bartosz Golaszewski
2025-06-11 8:15 ` Linus Walleij
2025-06-10 14:38 ` [PATCH RFC/RFT 03/15] gpio: sysfs: call mutex_destroy() in gpiod_unexport() Bartosz Golaszewski
2025-06-11 8:16 ` Linus Walleij
2025-06-10 14:38 ` [PATCH RFC/RFT 04/15] gpio: sysfs: refactor the coding style Bartosz Golaszewski
2025-06-11 8:16 ` Linus Walleij
2025-06-10 14:38 ` [PATCH RFC/RFT 05/15] gpio: sysfs: remove unneeded headers Bartosz Golaszewski
2025-06-11 8:17 ` Linus Walleij
2025-06-10 14:38 ` [PATCH RFC/RFT 06/15] gpio: sysfs: remove the mockdev pointer from struct gpio_device Bartosz Golaszewski
2025-06-11 8:19 ` Linus Walleij
2025-06-10 14:38 ` [PATCH RFC/RFT 07/15] gpio: sysfs: add a parallel class device for each GPIO chip using device IDs Bartosz Golaszewski
2025-06-11 8:27 ` Linus Walleij
2025-06-23 8:02 ` Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 08/15] gpio: sysfs: only get the dirent reference for the value attr once Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 09/15] gpio: sysfs: pass gpiod_data directly to internal GPIO sysfs functions Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 10/15] gpio: sysfs: don't use driver data in sysfs callbacks for line attributes Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 11/15] gpio: sysfs: rename the data variable in gpiod_(un)export() Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 12/15] gpio: sysfs: don't look up exported lines as class devices Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 13/15] gpio: sysfs: export the GPIO directory locally in the gpiochip<id> directory Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 14/15] gpio: sysfs: allow disabling the legacy parts of the GPIO sysfs interface Bartosz Golaszewski
2025-06-10 14:38 ` [PATCH RFC/RFT 15/15] gpio: TODO: remove the task for the sysfs rework Bartosz Golaszewski
2025-06-13 8:02 ` [PATCH RFC/RFT 00/15] gpio: sysfs: add a per-chip export/unexport attribute pair Geert Uytterhoeven
2025-06-16 12:27 ` Bartosz Golaszewski
2025-06-18 13:38 ` Jan Lübbe
2025-06-18 14:53 ` Bartosz Golaszewski
2025-06-18 15:56 ` Bartosz Golaszewski
2025-06-23 8:27 ` Jan Lübbe [this message]
2025-06-18 14:54 ` Bartosz Golaszewski
2025-06-20 7:30 ` (subset) " Bartosz Golaszewski
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=e3cb14a8e1a6ea1e9a050f8013730e56f79f62ec.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=warthog618@gmail.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).