From: Steven Eckhoff <steven.eckhoff.opensource@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel][PATCH 2/3] ASoC: TSCS42xx: Remove Playback/Capture in names
Date: Wed, 20 Jun 2018 12:34:53 -0500 [thread overview]
Message-ID: <20180620173451.GA3900@t7-ThinkPad-E560> (raw)
In-Reply-To: <20180618113154.GC6928@sirena.org.uk>
On Mon, Jun 18, 2018 at 12:31:54PM +0100, Mark Brown wrote:
> Really? They're part of the spec so it indicates that the apps have a
> problem...
I apologize for the delayed response.
I am unable to reproduce the issue that I was seeing with controls that
had Playback or Capture in their names. I am going look into this
further.
I was seeing an issue with amixer set where it would not find the
control, but I could use the numid. I wanted to make sure that it would
always work, so I could provide amixer set commands using the name of
the control in our documentation.
Regards,
Steven
next prev parent reply other threads:[~2018-06-20 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 20:45 [alsa-devel][PATCH 0/3] ASoC: TSCS42xx: Control Improvements Steven Eckhoff
2018-06-04 20:45 ` [alsa-devel][PATCH 1/3] ASoC: TSCS42xx: Add mic bias boost control Steven Eckhoff
2018-06-18 11:59 ` Applied "ASoC: TSCS42xx: Add mic bias boost control" to the asoc tree Mark Brown
2018-06-04 20:46 ` [alsa-devel][PATCH 2/3] ASoC: TSCS42xx: Remove Playback/Capture in names Steven Eckhoff
2018-06-18 11:31 ` Mark Brown
2018-06-20 17:34 ` Steven Eckhoff [this message]
2018-06-18 11:59 ` Applied "ASoC: TSCS42xx: Remove Playback/Capture in names" to the asoc tree Mark Brown
2018-06-04 20:47 ` [alsa-devel][PATCH 3/3] ASoC: TSCS42xx: Add headphone auto switching Steven Eckhoff
2018-06-18 11:59 ` Applied "ASoC: TSCS42xx: Add headphone auto switching" 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=20180620173451.GA3900@t7-ThinkPad-E560 \
--to=steven.eckhoff.opensource@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
Powered by JetHome