From: Kent Gibson <warthog618@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Marek Vasut" <marex@denx.de>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Jan Lübbe" <jlu@pengutronix.de>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: Replacing global GPIO numbers in sysfs with hardware offsets
Date: Wed, 5 Mar 2025 16:41:03 +0800 [thread overview]
Message-ID: <20250305084103.GA125901@rigel> (raw)
In-Reply-To: <CACRpkdaQ6EwkN+139Gn4Xe=RsOthv-GNwaFJGvUdDF53SL9BMA@mail.gmail.com>
On Wed, Mar 05, 2025 at 09:22:42AM +0100, Linus Walleij wrote:
> On Fri, Feb 28, 2025 at 10:53 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>
> > Let's keep it simple, and similar/identical to the existing API?
> >
> > Is there anything in Documentation/ABI/obsolete/sysfs-gpio
> > we can drop? edge?
>
> I suggested dropping all of the irq stuff earlier in the
> thread, given how bad quality it is. Especially if it's edge
> triggered it can easily squash 100 or 1000 IRQs into one
> fsnotify event.
>
+1 for removing edge and poll(2) on value. Keep the sysfs as a very
basic set/get interface for environments where ioctl()s are too
burdensome.
Not sure that active_low serves any purpose other than adding confusion.
Drop active_low and only support physical levels?
Cheers,
Kent.
next prev parent reply other threads:[~2025-03-05 8:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 12:45 Replacing global GPIO numbers in sysfs with hardware offsets Bartosz Golaszewski
2025-02-03 14:23 ` Geert Uytterhoeven
2025-02-07 20:18 ` Bartosz Golaszewski
2025-02-09 9:40 ` Geert Uytterhoeven
2025-02-25 18:25 ` Ayush Singh
2025-02-25 20:20 ` Linus Walleij
2025-02-26 6:25 ` Ayush Singh
2025-02-14 9:14 ` Linus Walleij
2025-02-21 18:01 ` Marek Vasut
2025-02-25 19:54 ` Linus Walleij
2025-02-26 12:36 ` Marek Vasut
2025-02-26 19:07 ` Bartosz Golaszewski
2025-02-28 7:49 ` Linus Walleij
2025-02-28 8:49 ` Geert Uytterhoeven
2025-02-28 8:55 ` Linus Walleij
2025-02-28 9:53 ` Geert Uytterhoeven
2025-03-05 8:22 ` Linus Walleij
2025-03-05 8:41 ` Kent Gibson [this message]
2025-03-11 10:28 ` Bartosz Golaszewski
2025-03-11 10:52 ` Geert Uytterhoeven
2025-03-11 11:53 ` Bartosz Golaszewski
2025-03-11 15:26 ` Geert Uytterhoeven
2025-02-21 19:56 ` Ahmad Fatoum
2025-02-25 19:56 ` Linus Walleij
2025-02-24 1:49 ` Kent Gibson
2025-02-24 8:28 ` Geert Uytterhoeven
2025-02-26 9:23 ` Bartosz Golaszewski
2025-02-26 10:58 ` Kent Gibson
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=20250305084103.GA125901@rigel \
--to=warthog618@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=jlu@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=marex@denx.de \
/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 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.