From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 1/2] ASoC: Intel: byt-rt5640: Update internal mic and speaker kcontrol names
Date: Tue, 25 Feb 2014 13:43:53 +0000 [thread overview]
Message-ID: <1393335833.2300.13.camel@loki> (raw)
In-Reply-To: <1393334248-29033-1-git-send-email-jarkko.nikula@linux.intel.com>
On Tue, 2014-02-25 at 15:17 +0200, Jarkko Nikula wrote:
> Use more sensible kcontrol names than "Int Mic" and "Ext Spk". Speakers
> especially are usually integrated devices in sales models.
>
> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> ---
> sound/soc/intel/byt-rt5640.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/sound/soc/intel/byt-rt5640.c b/sound/soc/intel/byt-rt5640.c
> index 038547b48b2d..672fedbfa680 100644
> --- a/sound/soc/intel/byt-rt5640.c
> +++ b/sound/soc/intel/byt-rt5640.c
> @@ -29,27 +29,27 @@
> static const struct snd_soc_dapm_widget byt_rt5640_widgets[] = {
> SND_SOC_DAPM_HP("Headphone", NULL),
> SND_SOC_DAPM_MIC("Headset Mic", NULL),
> - SND_SOC_DAPM_MIC("Int Mic", NULL),
> - SND_SOC_DAPM_SPK("Ext Spk", NULL),
> + SND_SOC_DAPM_MIC("Internal Mic", NULL),
> + SND_SOC_DAPM_SPK("Speaker", NULL),
> };
>
> static const struct snd_soc_dapm_route byt_rt5640_audio_map[] = {
> {"IN2P", NULL, "Headset Mic"},
> {"IN2N", NULL, "Headset Mic"},
> - {"DMIC1", NULL, "Int Mic"},
> + {"DMIC1", NULL, "Internal Mic"},
> {"Headphone", NULL, "HPOL"},
> {"Headphone", NULL, "HPOR"},
> - {"Ext Spk", NULL, "SPOLP"},
> - {"Ext Spk", NULL, "SPOLN"},
> - {"Ext Spk", NULL, "SPORP"},
> - {"Ext Spk", NULL, "SPORN"},
> + {"Speaker", NULL, "SPOLP"},
> + {"Speaker", NULL, "SPOLN"},
> + {"Speaker", NULL, "SPORP"},
> + {"Speaker", NULL, "SPORN"},
> };
>
> static const struct snd_kcontrol_new byt_rt5640_controls[] = {
> SOC_DAPM_PIN_SWITCH("Headphone"),
> SOC_DAPM_PIN_SWITCH("Headset Mic"),
> - SOC_DAPM_PIN_SWITCH("Int Mic"),
> - SOC_DAPM_PIN_SWITCH("Ext Spk"),
> + SOC_DAPM_PIN_SWITCH("Internal Mic"),
> + SOC_DAPM_PIN_SWITCH("Speaker"),
> };
>
> static int byt_rt5640_hw_params(struct snd_pcm_substream *substream,
> @@ -113,8 +113,8 @@ static int byt_rt5640_init(struct snd_soc_pcm_runtime *runtime)
>
> snd_soc_dapm_enable_pin(dapm, "Headset Mic");
> snd_soc_dapm_enable_pin(dapm, "Headphone");
> - snd_soc_dapm_enable_pin(dapm, "Ext Spk");
> - snd_soc_dapm_enable_pin(dapm, "Int Mic");
> + snd_soc_dapm_enable_pin(dapm, "Speaker");
> + snd_soc_dapm_enable_pin(dapm, "Internal Mic");
>
> snd_soc_dapm_sync(dapm);
> return ret;
Both
Acked-by: Liam Girdwoood <liam.r.girdwood@linux.intel.com>
next prev parent reply other threads:[~2014-02-25 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 13:17 [PATCH 1/2] ASoC: Intel: byt-rt5640: Update internal mic and speaker kcontrol names Jarkko Nikula
2014-02-25 13:17 ` [PATCH 2/2] ASoC: Intel: byt-rt5640: Use init time DAI format Jarkko Nikula
2014-02-25 13:43 ` Liam Girdwood [this message]
2014-02-25 23:49 ` [PATCH 1/2] ASoC: Intel: byt-rt5640: Update internal mic and speaker kcontrol names 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=1393335833.2300.13.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox