linux-kernel - Re: [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical presence

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] [day] [month] [year] [list]

Message-ID: <20120502230322.GB19693@opensource.wolfsonmicro.com>
Date:	Thu, 3 May 2012 00:03:22 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Donggeun Kim <dg77.kim@...sung.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical
	presence

On Wed, May 02, 2012 at 01:13:21PM -0700, Greg Kroah-Hartman wrote:

> Ok, but where is the in-kernel user of this new interface?  Why are we
> adding it now before someone actually needs it?

Well, one could say the same thing about the entire interface right now
but if you look at the existing accessory detection abstraction for
sound cards in include/sound/jack.h and the input API that's currently
the only userspace API for it you can see that they have this feature
already.

There's a reasonable prospect of the ALSA abstraction getting support
for extcon at some point in the not too distant future at which point it
will acquire all the users that has but I'd not anticipate that until
after the merge window as the ALSA stuff wants some prodding and poking 
prior to doing that which I really hope will collide with some other
updates too.

> And shouldn't this also update some documentation somewhere as well?

There doesn't appear to be any existing relevant documentation to
update, and to be honest given that what we're doing is mapping a plain
text name into a constant I'm not sure it'd be adding much.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/