All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Kevin Hilman <khilman@kernel.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH] gpio: omap: make gpio numbering deterministical by using of aliases
Date: Wed, 15 Jun 2016 01:27:06 -0700	[thread overview]
Message-ID: <20160615082705.GW22406@atomide.com> (raw)
In-Reply-To: <20160615072404.GB26768@pengutronix.de>

* 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.

Naturally I don't have any objections for adding a character device :)

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] gpio: omap: make gpio numbering deterministical by using of aliases
Date: Wed, 15 Jun 2016 01:27:06 -0700	[thread overview]
Message-ID: <20160615082705.GW22406@atomide.com> (raw)
In-Reply-To: <20160615072404.GB26768@pengutronix.de>

* 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.

Naturally I don't have any objections for adding a character device :)

Regards,

Tony

  reply	other threads:[~2016-06-15  8:27 UTC|newest]

Thread overview: 34+ 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 10:03 ` Uwe Kleine-König
2016-06-14 11:18 ` Grygorii Strashko
2016-06-14 11:18   ` Grygorii Strashko
2016-06-14 12:01   ` Uwe Kleine-König
2016-06-14 12:01     ` Uwe Kleine-König
2016-06-14 15:10     ` Grygorii Strashko
2016-06-14 15:10       ` Grygorii Strashko
2016-06-15  0:00 ` kbuild test robot
2016-06-15  0:00   ` kbuild test robot
2016-06-15  6:56 ` Linus Walleij
2016-06-15  6:56   ` Linus Walleij
2016-06-15  7:24   ` Uwe Kleine-König
2016-06-15  7:24     ` Uwe Kleine-König
2016-06-15  8:27     ` Tony Lindgren [this message]
2016-06-15  8:27       ` Tony Lindgren
2016-06-15  9:56       ` Grygorii Strashko
2016-06-15  9:56         ` Grygorii Strashko
2016-06-18  8:30         ` Linus Walleij
2016-06-18  8:30           ` Linus Walleij
2016-06-18  8:29       ` Linus Walleij
2016-06-18  8:29         ` Linus Walleij
2016-06-18  8:25     ` Linus Walleij
2016-06-18  8:25       ` Linus Walleij
2016-06-19  1:08       ` Uwe Kleine-König
2016-06-19  1:08         ` Uwe Kleine-König
2016-06-22 16:16         ` Mark Rutland
2016-06-22 16:16           ` Mark Rutland
2016-06-23  9:04           ` Linus Walleij
2016-06-23  9:04             ` Linus Walleij
2016-06-23  9:38             ` Grygorii Strashko
2016-06-23  9:38               ` Grygorii Strashko
2016-06-23 12:08               ` Linus Walleij
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=20160615082705.GW22406@atomide.com \
    --to=tony@atomide.com \
    --cc=gnurou@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=kernel@pengutronix.de \
    --cc=khilman@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=u.kleine-koenig@pengutronix.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.