[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130919183506.GJ21013@sirena.org.uk>
Date: Thu, 19 Sep 2013 19:35:06 +0100
From: Mark Brown <broonie@...nel.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Mark Rutland <mark.rutland@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
Pawel Moll <Pawel.Moll@....com>,
Stephen Warren <swarren@...dotorg.org>,
Ian Campbell <ian.campbell@...rix.com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
Kishon Vijay Abraham I <kishon@...com>
Subject: Re: [RFC PATCH 5/6] extcon-gpio: Describe devicetree bindings
On Thu, Sep 19, 2013 at 11:28:50AM -0700, Guenter Roeck wrote:
> On Thu, Sep 19, 2013 at 05:42:45PM +0100, Mark Brown wrote:
> > Many of the things described only have passive components attached, or
> > things that otherwise don't need drivers - things like power inputs or
> > headphone connectors, they're mainly providing information to allow
> > userspace to behave differently (eg, display a charging indicator in the
> > UI). It's not 100% true but by and by large if detection is being done
> > using a GPIO it's probably something like that.
> Correct. However, gpio based 'detect' pins typically need debounce support
> which is not directly available through the gpio userspace API. I tried to add
> that earlier, but was told to use extcon instead as it provides the necessary
> infrastructure. Now it almost looks like I can not use it either because the
> required devicetree bindings may be considered unacceptable.
Yes, I'm trying to explain to Mark why there are drivers just purely for
the connector without any software for the connected device.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists