From: Michael Welling <mwelling@ieee.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: Requesting as a GPIO a pin already used through pinctrl
Date: Thu, 22 Sep 2016 10:46:06 -0500 [thread overview]
Message-ID: <20160922154606.GA23980@deathstar> (raw)
In-Reply-To: <20160922104852.GO8719@lukather>
On Thu, Sep 22, 2016 at 01:48:52PM +0300, Maxime Ripard wrote:
> On Wed, Sep 21, 2016 at 03:34:35PM -0500, Michael Welling wrote:
> > On Wed, Sep 21, 2016 at 10:51:28PM +0300, Maxime Ripard wrote:
> > > Hi Linus,
> > >
> > > Thanks for your reply.
> > >
> > > On Sun, Sep 18, 2016 at 01:30:24PM +0200, Linus Walleij wrote:
> > > > On Fri, Sep 16, 2016 at 3:58 PM, Maxime Ripard
> > > > <maxime.ripard@free-electrons.com> wrote:
> > > >
> > > > > However, things are getting weird when you have that requested pin
> > > > > assigned to one device, and you try to export the GPIO on that pin
> > > > > (through sysfs for example,
> > > >
> > > > DON'T use sysfs. Use the new chardev ABI which is by the way enabled
> > > > by default.
> > > >
> > > > (But you will face the same issue there I guess.)
> > >
> > > Yeah, well, we could re-do the discussion on ksummit-discuss :)
> >
> > Are you guys trolling me?
>
> No, the point I was trying to make is that not every system and
> product kernel out there has been switched to a 4.8+ kernel, for
> exactly the reasons that are discussed right now on ksummit-discuss.
>
Ah thanks for explaining. I read through the latest posts and assume you are
talking about the lengthy backporting discussion.
> I don't really get how that is trolling.
Nevermind that. I thought you were referring to my one and only post to that list.
https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2015-July/001879.html
Sorry for the noise.
>
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
next prev parent reply other threads:[~2016-09-22 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:58 Requesting as a GPIO a pin already used through pinctrl Maxime Ripard
2016-09-18 11:30 ` Linus Walleij
2016-09-21 19:51 ` Maxime Ripard
2016-09-21 20:34 ` Michael Welling
2016-09-22 10:48 ` Maxime Ripard
2016-09-22 15:46 ` Michael Welling [this message]
2016-09-23 13:22 ` Linus Walleij
2016-09-23 15:24 ` Vladimir Zapolskiy
2016-09-23 21:34 ` Maxime Ripard
2016-09-30 16:26 ` Linus Walleij
2016-09-23 21:05 ` Maxime Ripard
2016-10-26 15:49 ` Maxime Ripard
2016-10-27 12:12 ` Linus Walleij
2016-11-02 21:31 ` Maxime Ripard
2016-11-06 10:11 ` 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=20160922154606.GA23980@deathstar \
--to=mwelling@ieee.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=nicolas.ferre@atmel.com \
/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).