All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: John Hsu <KCHSU0@nuvoton.com>
Cc: WTLI@nuvoton.com, YHCHuang@nuvoton.com,
	alsa-devel@alsa-project.org, CTLIN0@nuvoton.com,
	lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: nau8824: user configuration of key detection
Date: Thu, 22 Mar 2018 10:07:14 +0800	[thread overview]
Message-ID: <20180322020714.GA2186@sirena.org.uk> (raw)
In-Reply-To: <1521617423-2213-1-git-send-email-KCHSU0@nuvoton.com>


[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]

On Wed, Mar 21, 2018 at 03:30:23PM +0800, John Hsu wrote:
> The SAR ADC of key press detection varies depending on headset.
> We can't make a set of common threshold values for every case.
> Therefore, the driver provides configuration for user and
> they can set up values by UCM configuration.

It's more normal for this configuration to be done as part of the
platform bindings for the device, with the values being tuned based on
the in box headset and the tastes of the system integrator, seeing this
exposed as a userspace control is a bit surprising - what motivated
that?

If we are going to have this tunable from userspace we probably want a
standard interface for it so that the userspace software can work more
generally.  However that's a bit tricky as the tunable parameters are
going to vary...

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-03-22  2:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21  7:30 [PATCH] ASoC: nau8824: user configuration of key detection John Hsu
2018-03-22  2:07 ` Mark Brown [this message]
2018-03-22  2:41   ` John Hsu
2018-04-17 17:09 ` Applied "ASoC: nau8824: user configuration of key detection" to the asoc tree Mark Brown
2018-04-17 17:11 ` Mark Brown

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=20180322020714.GA2186@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=CTLIN0@nuvoton.com \
    --cc=KCHSU0@nuvoton.com \
    --cc=WTLI@nuvoton.com \
    --cc=YHCHuang@nuvoton.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.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.