alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	lee.jones@linaro.org, lgirdwood@gmail.com
Subject: [PATCH 0/5] Add support for trigger only voice recognition
Date: Fri, 13 May 2016 16:45:14 +0100	[thread overview]
Message-ID: <1463154319-10070-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)

In some systems our voice trigger firmwares will be used only to
provide an event that indicates the trigger phrase was spoken,
this patch chain adds support for this use-case. There are two
parts to adding this support firstly, a mechanism is required
to get the DSP to power on without the compressed stream being
opened, this is done by means of a virtual output for the voice
trigger in the DAPM graph. Secondly, the trigger event needs to
be handled. Typically this will be used to generate a key press
event, but there are numerous options what could be done here,
and vendors often have their own rather strong opinions.  Rather
than dictate the usage at the driver level we we simply provide a
notifier that can be caught in the machine driver and appropriate
action can be taken there.

Thanks,
Charles

Charles Keepax (5):
  ASoC: arizona: Tie SYSCLK to DRC signal activity widgets
  ASoC: arizona: Add voice trigger output widget
  ASoC: wm_adsp: Specifically propagate voice trigger event to caller
  ASoC: arizona: Add a notifier chain for CODEC events
  ASoC: arizona: Add event notification on voice trigger events

 include/linux/mfd/arizona/core.h | 10 ++++++++++
 sound/soc/codecs/arizona.c       | 43 ++++++++++++++++++++++++++++++++++++++++
 sound/soc/codecs/arizona.h       | 15 ++++++++++++++
 sound/soc/codecs/cs47l24.c       | 16 +++++++++++++++
 sound/soc/codecs/wm5102.c        |  1 +
 sound/soc/codecs/wm5110.c        | 16 +++++++++++++++
 sound/soc/codecs/wm8998.c        |  1 +
 sound/soc/codecs/wm_adsp.c       |  5 +++++
 sound/soc/codecs/wm_adsp.h       |  4 ++++
 9 files changed, 111 insertions(+)

-- 
2.1.4

             reply	other threads:[~2016-05-13 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 15:45 Charles Keepax [this message]
2016-05-13 15:45 ` [PATCH 1/5] ASoC: arizona: Tie SYSCLK to DRC signal activity widgets Charles Keepax
2016-05-14 10:13   ` Applied "ASoC: arizona: Tie SYSCLK to DRC signal activity widgets" to the asoc tree Mark Brown
2016-05-13 15:45 ` [PATCH 2/5] ASoC: arizona: Add voice trigger output widget Charles Keepax
2016-05-14 10:12   ` Applied "ASoC: arizona: Add voice trigger output widget" to the asoc tree Mark Brown
2016-05-13 15:45 ` [PATCH 3/5] ASoC: wm_adsp: Specifically propagate voice trigger event to caller Charles Keepax
2016-05-14 10:12   ` Applied "ASoC: wm_adsp: Specifically propagate voice trigger event to caller" to the asoc tree Mark Brown
2016-05-13 15:45 ` [PATCH 4/5] ASoC: arizona: Add a notifier chain for CODEC events Charles Keepax
2016-05-27 20:46   ` Applied "ASoC: arizona: Add a notifier chain for CODEC events" to the asoc tree Mark Brown
2016-05-13 15:45 ` [PATCH 5/5] ASoC: arizona: Add event notification on voice trigger events Charles Keepax
2016-05-27 20:46   ` Applied "ASoC: arizona: Add event notification on voice trigger events" to the asoc tree 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=1463154319-10070-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=patches@opensource.wolfsonmicro.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).