From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: David Rhodes <david.rhodes@cirrus.com>
Cc: patches@opensource.cirrus.com, alsa-devel@alsa-project.org,
broonie@kernel.org, lgirdwood@gmail.com, Li Xu <li.xu@cirrus.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: wm_adsp: Expose mixer control API
Date: Mon, 18 Nov 2019 13:46:02 +0000 [thread overview]
Message-ID: <20191118134602.GH10439@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <1573847653-17094-2-git-send-email-david.rhodes@cirrus.com>
On Fri, Nov 15, 2019 at 01:54:13PM -0600, David Rhodes wrote:
> From: Li Xu <li.xu@cirrus.com>
>
> Expose mixer control API for reading and writing controls from the kernel.
> This API can be used by ALSA kernel drivers with ADSP support to
> read and write firmware-defined memory regions.
>
> Signed-off-by: Li Xu <li.xu@cirrus.com>
> Signed-off-by: David Rhodes <david.rhodes@cirrus.com>
> ---
Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-18 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 19:54 [alsa-devel] [PATCH v2] ASoC: wm_adsp: Expose mixer control API David Rhodes
2019-11-15 19:54 ` [alsa-devel] [PATCH] " David Rhodes
2019-11-18 13:46 ` Charles Keepax [this message]
2019-11-18 17:48 ` [alsa-devel] Applied "ASoC: wm_adsp: Expose mixer control API" to the asoc tree Mark Brown
2019-11-18 11:51 ` [alsa-devel] [PATCH v2] ASoC: wm_adsp: Expose mixer control API Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2019-10-31 19:36 [alsa-devel] [PATCH] " David Rhodes
2019-11-04 9:47 ` Charles Keepax
2019-11-04 12:58 ` 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=20191118134602.GH10439@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=david.rhodes@cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=li.xu@cirrus.com \
--cc=patches@opensource.cirrus.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.