From: Markus Pargmann <mpa@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: 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 11:13:16 +0200 [thread overview]
Message-ID: <20151006091316.GK19355@pengutronix.de> (raw)
In-Reply-To: <CACRpkdZBw7ayenkRTtpQH==G64TGNEXv6DgzdRAZxCCHJUZuRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
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?
Any chance that you both are at the ELCE?
Best Regards,
Markus
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-06 9:13 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 [this message]
2015-10-06 14:09 ` Johan Hovold
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=20151006091316.GK19355@pengutronix.de \
--to=mpa@pengutronix.de \
--cc=acourbot@nvidia.com \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
/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).