From: grygorii.strashko@ti•com (Grygorii Strashko)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] gpio: omap: make gpio numbering deterministical by using of aliases
Date: Wed, 15 Jun 2016 12:56:47 +0300 [thread overview]
Message-ID: <5761265F.2050508@ti.com> (raw)
In-Reply-To: <20160615082705.GW22406@atomide.com>
On 06/15/2016 11:27 AM, Tony Lindgren wrote:
> * Uwe Kleine-K?nig <u.kleine-koenig@pengutronix•de> [160615 00:27]:
>> On Wed, Jun 15, 2016 at 08:56:58AM +0200, Linus Walleij wrote:
>>> The way forward is to use the character device and use gpiochip
>>> devices with offset indexes and look up GPIOs by name from the
>>> character devices. If nothing substantial happens I am merging the
>>> final pieces of the GPIO chardev ABI for v4.8 and that is doing all that
>>> sysfs was doing and then some. I just need to change a small thing
>>> before sending the final version for review.
>>
>> Hmm, so /sys/class/gpio was obsoleted before the substitution was ready?
>> I'd say an overlapping of several kernel versions would be good as we
>> cannot expect that userspace changes as fast as the kernel.
>
> Well the /sys/class/gpio is an interface, and we'll have to maintain
> it basically forever as we all know. It also works just fine for simple
> things, so let's make sure it is usable. Having it inconsistent can
> cause nasty side effects upgrading kernels.
>
Wouldn't gpio-line-names be helpful for such cases as mentioned in [1],[2]
But I don't know it these properties were exposed in legacy GPIO sysfs interface also.
[1] http://www.spinics.net/lists/linux-gpio/msg15040.html
[2] https://patchwork.ozlabs.org/patch/617713/
--
regards,
-grygorii
next prev parent reply other threads:[~2016-06-15 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 10:03 [PATCH] gpio: omap: make gpio numbering deterministical by using of aliases Uwe Kleine-König
2016-06-14 11:18 ` Grygorii Strashko
2016-06-14 12:01 ` Uwe Kleine-König
2016-06-14 15:10 ` Grygorii Strashko
2016-06-15 0:00 ` kbuild test robot
2016-06-15 6:56 ` Linus Walleij
2016-06-15 7:24 ` Uwe Kleine-König
2016-06-15 8:27 ` Tony Lindgren
2016-06-15 9:56 ` Grygorii Strashko [this message]
2016-06-18 8:30 ` Linus Walleij
2016-06-18 8:29 ` Linus Walleij
2016-06-18 8:25 ` Linus Walleij
2016-06-19 1:08 ` Uwe Kleine-König
2016-06-22 16:16 ` Mark Rutland
2016-06-23 9:04 ` Linus Walleij
2016-06-23 9:38 ` Grygorii Strashko
2016-06-23 12:08 ` Linus Walleij
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=5761265F.2050508@ti.com \
--to=grygorii.strashko@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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