From: Mark Brown <broonie@kernel.org>
To: John Hsu <KCHSU0@nuvoton.com>
Cc: AP MS30 Linux ALSA <alsa-devel@alsa-project.org>,
"anatol.pomozov@gmail.com" <anatol.pomozov@gmail.com>,
AC30 YHChuang <YHCHuang@nuvoton.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"benzh@chromium.org" <benzh@chromium.org>,
AC30 CTLin0 <CTLIN0@nuvoton.com>, MS40 MHKuo <MHKuo@nuvoton.com>,
"yong.zhi@intel.com" <yong.zhi@intel.com>
Subject: Re: [PATCH 1/2 v2] ASoC: nau8825: non-clock jack detection for power saving at standby
Date: Mon, 30 May 2016 16:16:38 +0100 [thread overview]
Message-ID: <20160530151638.GN29837@sirena.org.uk> (raw)
In-Reply-To: <574B9ED3.5070005@nuvoton.com>
[-- Attachment #1.1: Type: text/plain, Size: 279 bytes --]
On Mon, May 30, 2016 at 10:00:51AM +0800, John Hsu wrote:
> I see. The configuration is an array of filter coefficients. Maybe
> we'll make it with bytes type kcontrol for userspace. Is it suitable
> for the case?
Right, byte controls would be completely uncontroversial here.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-05-30 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 9:17 [PATCH 1/2 v2] ASoC: nau8825: non-clock jack detection for power saving at standby John Hsu
2016-05-13 10:48 ` Mark Brown
2016-05-16 1:47 ` John Hsu
2016-05-18 17:05 ` Mark Brown
2016-05-20 3:12 ` John Hsu
2016-05-20 11:01 ` Mark Brown
2016-05-23 1:59 ` John Hsu
2016-05-23 17:04 ` Mark Brown
2016-05-24 3:41 ` John Hsu
2016-05-24 11:03 ` Mark Brown
2016-05-30 2:00 ` John Hsu
2016-05-30 15:16 ` Mark Brown [this message]
2016-05-13 13:26 ` Applied "ASoC: nau8825: non-clock jack detection for power saving at standby" to the asoc tree Mark Brown
2016-05-13 13:34 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2016-05-16 8:55 [PATCH 1/2 v2] ASoC: nau8825: non-clock jack detection for power saving at standby John Hsu
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=20160530151638.GN29837@sirena.org.uk \
--to=broonie@kernel.org \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=MHKuo@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=benzh@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=yong.zhi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).