linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
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>,
	Markus Pargmann <mpa@pengutronix.de>
Subject: Re: [PATCH] gpio: keep the GPIO line names internal
Date: Mon, 5 Oct 2015 11:01:47 +0100	[thread overview]
Message-ID: <20151005100147.GB25143@localhost> (raw)
In-Reply-To: <CACRpkdaB=Sne1Vq=apQE5r8FDvfvQ-4w0nths-dVnuJvBaGDOA@mail.gmail.com>

On Mon, Oct 05, 2015 at 10:54:52AM +0200, Linus Walleij wrote:
> On Sun, Oct 4, 2015 at 3:37 PM, Johan Hovold <johan@kernel.org> wrote:
> 
> > This looks good (apart from the checkpatch warning for the warning
> > message string).
> 
> Yeah the GPIO maintainer is liberal about that rule...

Heh. I'm sticking to the 80 column limit too, but having grepable error
messages do have its merit.

> > You also need to revert ddd5404007b8 ("gpio-sysfs: Use gpio descriptor
> > name instead of gpiochip names array") however as this is an ABI change.
> > Otherwise pins with a name in DT will now be exported using the gpio name
> > rather than number as they used to be. [ The current behaviour is
> > maintained by exporting names from chip->names for hard coded names
> > only. ]
> 
> 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?

This means that a pin used today from userspace, can not be initialised
using this mechanism without breaking the ABI.

My suggestion is to leave gpiolib-sysfs.c as is, and make sure to limit
the name export to legacy board files as before.

Thanks,
Johan

  reply	other threads:[~2015-10-05 10:00 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 [this message]
2015-10-05 11:07       ` Linus Walleij
2015-10-06  9:13         ` Markus Pargmann
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=20151005100147.GB25143@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).