linux-kernel - Re: [PATCH v5 2/5] Extcon: support notification based on the state changes.

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:	Sun, 19 Feb 2012 18:20:10 -0800
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	MyungJoo Ham <myungjoo.ham@...sung.com>
Cc:	linux-kernel@...r.kernel.org, NeilBrown <neilb@...e.de>,
	Randy Dunlap <rdunlap@...otime.net>,
	Mike Lockwood <lockwood@...roid.com>,
	Arve Hjønnevag <arve@...roid.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Donggeun Kim <dg77.kim@...sung.com>, Greg KH <gregkh@...e.de>,
	Arnd Bergmann <arnd@...db.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Morten CHRISTIANSEN <morten.christiansen@...ricsson.com>,
	John Stultz <john.stultz@...aro.org>,
	Joerg Roedel <joerg.roedel@....com>, myungjoo.ham@...il.com
Subject: Re: [PATCH v5 2/5] Extcon: support notification based on the state
 changes.

On Fri, Feb 10, 2012 at 03:40:35PM +0900, MyungJoo Ham wrote:
> From: Donggeun Kim <dg77.kim@...sung.com>

> State changes of extcon devices have been notified via kobjet_uevent.
> This patch adds notifier interfaces in order to allow device drivers to
> get notified easily. Along with notifier interface,
> extcon_get_extcon_dev() function is added so that device drivers may
> discover a extcon_dev easily.

Reviewed-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>

This is something I'd been going to ask for.  One related thing which
needs some thought is how we combine extcon detection methods for
hardware which uses multiple unrelated detection methods.  One of the
common examples for audio jacks is that you might have an ultra low
power detection method for detecting if something is physically present
in the jack and then use that to start up additional detection methods
that can tell what that thing actually is.  The two provide different
pieces of the picture reported to userspace.

With the ALSA and input accessory reporting methods we've got bitmasks
so this can be implemented fairly naturally but with the ABI that we've
got from Android here things aren't so easy as we need to go down to a
single value.  Perhaps some sort of bitmask to value translation layer?

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