On Fri, Mar 09, 2012 at 05:26:26PM +0900, MyungJoo Ham wrote:
> On Mon, Mar 5, 2012 at 9:07 PM, Mark Brown

> > The issue is the combination of the naming (h2w isn't very meaningful
> > and only works with a single jack) and the magic numbers used for
> > reporting state, plus the registration collisions.  Existing code can be
> > ported over fairly easily but it's got issues as an ABI which we'd want
> > to fix.

> The ABI of simply ported (only with API name changes) ex-switch extcon
> device won't be changed:

> Or, do you mean that extcon class should support not ex-swtich extcon
> device drivers such as adc-jack.c (not ported from oldies) to support
> "legacy" userspace application that is aware of only switch interface?

Neither of these, I mean that we'll probably want to do some updates to
the drivers as they go into mainline which will change their interface
beyond the simple s/switch/extcon/ change.