linux-kernel - Re: [PATCH v8 resend 6/6] Documentation/extcon: porting guide for Android kernel switch driver.

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]

Message-ID: <20120420215902.GA3088@opensource.wolfsonmicro.com>
Date:	Fri, 20 Apr 2012 22:59:03 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Arnd Bergmann <arnd@...db.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Arve Hjønnevag <arve@...roid.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Morten CHRISTIANSEN <morten.christiansen@...ricsson.com>,
	John Stultz <john.stultz@...aro.org>, myungjoo.ham@...il.com,
	cw00.choi@...sung.com
Subject: Re: [PATCH v8 resend 6/6] Documentation/extcon: porting guide for
 Android kernel switch driver.

On Fri, Apr 20, 2012 at 10:15:34AM -0700, Greg KH wrote:
> On Fri, Apr 20, 2012 at 06:05:20PM +0100, Mark Brown wrote:

> > Every phone with a headset jack will have at least one switch if it's
> > running on Android.  People doing system integration will generally need
> > to know about this, at least until we've got the ALSA detection stuff
> > integrated with extcon.

> Ok, but where are those drivers at?  Any pointers to them so I can start
> sucking them into the tree and doing this conversion?

The actual code is all obviously out of tree, I'd expect any Android BSP
to contain at least some usage of it (though often just the basic GPIO
one for CPU vendor ones).

> Is this, and the wakelock stuff, holding back a torrent of drivers to be
> submitted somewhere?  Or are they buried in vendor trees, never to be
> seen?

I'd not characterise it as a massive problem (and wakelocks won't hold
back anything that doesn't have other problems).  I suspect that the
code for a Samsung phone with the 30 pin connector will show something
interesting, though I can't say I've actually looked.  For things like
headset detection there's already ways to support things in mainline and
we should just end up hooking extcon into the central support for these
things.

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