From: Mark Brown <broonie@sirena.org.uk>
To: Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] tlv320aic3x: headset/button press support
Date: Tue, 2 Dec 2008 19:50:19 +0000 [thread overview]
Message-ID: <20081202195013.GA6972@sirena.org.uk> (raw)
In-Reply-To: <20081202163754.GA29550@buzzloop.caiaq.de>
On Tue, Dec 02, 2008 at 05:37:54PM +0100, Daniel Mack wrote:
> On Thu, Nov 27, 2008 at 11:50:21AM +0000, Mark Brown wrote:
> > > +#define AIC3X_HEADSET_DETECT_CELLULAR (2 << 5)
> > > +#define AIC3X_HEADSET_DETECT_BOTH (3 << 5)
> > What exactly is CELLULAR? A headset?
> There is different types of headsets supported by this chip (see page 42
> of the datasheet), and this bits define which types the detection should
> be enabled for.
I *belive* it's a headset but please submit a patch adding some text
documenting this, ideally people shouldn't have to refer to the
datasheet to use the driver.
> Best regards,
> Daniel
>
> ---
>
> - Add aic3x_set_headset_detection() function to define the headset detection
> mode for tlv32aic3x chips
> - added aic3x_button_pressed()
> - Read from the real-time registers in aic3x_headset_detected() to query
> headset presence without an occured interrupt
>
> Signed-off-by: Daniel Mack <daniel@caiaq.de>
As I have repeatedly mentioned it would be very much better if you were
to do your submissions in the standard fashion which is documented in
Documentation/SubmittingPatches. The fact that you don't do this makes
your patches more difficult to apply and doesn't encourage review.
Note in particular the --- above which causes your commit message to be
removed.
next prev parent reply other threads:[~2008-12-02 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 22:07 [PATCH] tlv320aic3x: headset/button press support Daniel Mack
2008-11-27 11:50 ` Mark Brown
2008-12-02 16:37 ` Daniel Mack
2008-12-02 19:50 ` Mark Brown [this message]
2008-12-03 10:39 ` Daniel Mack
2008-12-03 10:44 ` Daniel Mack
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=20081202195013.GA6972@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@caiaq.de \
/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.