Re: Requesting as a GPIO a pin already used through pinctrl

[Michael Welling <mwelling@xxxxxxxx>]

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@xxxxxxxxxxxxxxxxxx> 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


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