All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Donggeun Kim <dg77.kim@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical presence
Date: Thu, 3 May 2012 00:03:22 +0100	[thread overview]
Message-ID: <20120502230322.GB19693@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120502201321.GA26275@kroah.com>

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.

      reply	other threads:[~2012-05-02 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  9:38 [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical presence Mark Brown
2012-05-02 20:13 ` Greg Kroah-Hartman
2012-05-02 23:03   ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120502230322.GB19693@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=dg77.kim@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.