linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Markus Pargmann <mpa@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Johan Hovold <johan@kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH] gpio: keep the GPIO line names internal
Date: Tue, 6 Oct 2015 15:09:19 +0100	[thread overview]
Message-ID: <20151006140919.GF25143@localhost> (raw)
In-Reply-To: <20151006091316.GK19355@pengutronix.de>

On Tue, Oct 06, 2015 at 11:13:16AM +0200, Markus Pargmann wrote:
> On Mon, Oct 05, 2015 at 01:07:09PM +0200, Linus Walleij wrote:
> > On Mon, Oct 5, 2015 at 12:01 PM, Johan Hovold <johan@kernel.org> wrote:
> > 
> > >> I think it is ABI-correct: it uses desc->name if that is set, and
> > >> currently that is only set from chip->names[] so status quo.
> > >
> > > Yes, but this work was aiming at generalising the hogs so that they
> > > could later be requested (and exported), right?
> > 
> > Yeah something like so... thinking about it we should indeed
> > takes the names directly from chip->names[] for this, so we
> > can use the name field in the gpio descriptor for the "real"
> > chardev interface later.
> 
> So what is this "real" chardev interface all about? What are the
> requirements and features for such an interface? How is it supposed to
> work? Was this already discussed somewhere?

It has been discussed in various threads, often when someone proposes to
tweak the current sysfs interface to cater to their specific needs.

Several people have expressed ideas, but no more formal proposal for a
new userspace interface has been put forward yet. Since this will also
become ABI we need to get it right (this time).

> Any chance that you both are at the ELCE?

I'm here, but not Linus. I'll see if I can spot you.

Johan

  reply	other threads:[~2015-10-06 14:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 23:27 [PATCH] gpio: keep the GPIO line names internal Linus Walleij
2015-09-24  7:40 ` Markus Pargmann
2015-09-24 16:47   ` Linus Walleij
2015-10-04 13:37 ` Johan Hovold
2015-10-05  8:54   ` Linus Walleij
2015-10-05 10:01     ` Johan Hovold
2015-10-05 11:07       ` Linus Walleij
2015-10-06  9:13         ` Markus Pargmann
2015-10-06 14:09           ` Johan Hovold [this message]
2015-10-16 14:41           ` Linus Walleij
2015-10-05  9:47   ` Markus Pargmann
2015-10-05 10:07     ` Johan Hovold
2015-10-05 10:19       ` Markus Pargmann
2015-10-05 11:10         ` Johan Hovold

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=20151006140919.GF25143@localhost \
    --to=johan@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mpa@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 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).