linux-kernel - Re: [RFC PATCH 5/6] extcon-gpio: Describe devicetree bindings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Sep 2013 17:42:45 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Mark Rutland <mark.rutland@....com>
Cc:	Guenter Roeck <linux@...ck-us.net>,
	"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 Wed, Sep 18, 2013 at 04:38:28PM +0100, Mark Rutland wrote:
> On Mon, Sep 16, 2013 at 04:19:53PM +0100, Guenter Roeck wrote:

> > I think what you are saying is that describing a generic connector via
> > devicetree is not acceptable, even though it _does_ describe hardware.
> > I would have to describe a specific connector for a specific hardware
> > instead, which in turn would need its own driver. Is that correct ?

> Regardless of how the connector is described, the block of hardware it
> connects to will have to be described, and some description of the
> connector will be necessary (either in the node for the block, or by
> phandle to a node for the connector). I agree that having a combined IP
> block + connector driver for each permutation is not good.

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.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)