From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: oder_chiou@realtek.com, jack.yu@realtek.com,
alsa-devel@alsa-project.org, lars@metafoo.de,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
lgirdwood@gmail.com, broonie@kernel.org, derek.fang@realtek.com,
flove@realtek.com, shumingf@realtek.com, bard.liao@intel.com
Subject: Re: [PATCH] ASoC: rt715: add main capture switch and main capture volume control
Date: Mon, 14 Dec 2020 17:58:41 +0100 [thread overview]
Message-ID: <s5hk0tkqq7y.wl-tiwai@suse.de> (raw)
In-Reply-To: <0b0afd81-0595-c661-ec1e-e81b7e8f8fec@perex.cz>
On Mon, 14 Dec 2020 17:44:27 +0100,
Jaroslav Kysela wrote:
>
> >>> + * "Main Capture Volume" looks the same as "ADC 07 Capture Volume",
> >>
> >> I would just use "Capture Volume" and "Capture Switch" here without the Main
> >> prefix to follow other drivers.
> >
> > It's similar to the 'Master Capture Switch' used in HDaudio, what other
> > drivers were you referring to?
>
> HDAudio is using just 'Capture Switch' and 'Capture Volume' for the root
> capture controls plus the input selector (enum). The Master prefix is used
> only for the playback direction. And the word master is not prohibited for the
> audio context, is it?
Right, we keep the word Master in the sound API because it's deeply
bound with the actual use case.
Takashi
next prev parent reply other threads:[~2020-12-14 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 6:49 [PATCH] ASoC: rt715: add main capture switch and main capture volume control jack.yu
2020-12-14 7:35 ` Jaroslav Kysela
2020-12-14 15:07 ` Pierre-Louis Bossart
2020-12-14 16:44 ` Jaroslav Kysela
2020-12-14 16:58 ` Takashi Iwai [this message]
2020-12-14 17:12 ` Pierre-Louis Bossart
2020-12-15 10:39 ` Jaroslav Kysela
2020-12-15 16:00 ` Pierre-Louis Bossart
2020-12-15 16:27 ` Jaroslav Kysela
2020-12-15 17:05 ` Pierre-Louis Bossart
2020-12-15 17:31 ` Jaroslav Kysela
2021-01-05 8:11 ` Jack Yu
2021-01-06 9:39 ` Yang, Libin
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=s5hk0tkqq7y.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shumingf@realtek.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