From: Mark Brown <broonie@kernel.org>
To: Sergej Sawazki <ce3a@gmx.de>
Cc: ckeepax@opensource.wolfsonmicro.com, lars@metafoo.de,
lgirdwood@gmail.com, alsa-devel@alsa-project.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [RFC PATCH] ASoC: wm8741: Add differential mono mode support
Date: Tue, 5 May 2015 14:57:31 +0100 [thread overview]
Message-ID: <20150505135731.GF22845@sirena.org.uk> (raw)
In-Reply-To: <B33D8E95-F8F9-40B8-B9BC-6AA8734A4838@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 778 bytes --]
On Tue, May 05, 2015 at 02:19:38PM +0200, Sergej Sawazki wrote:
> The mono mode of the device should not be confused
> with the ALSA mono mode. If the device is in mono mode
> it either plays the left (mono left mode) or the right (mono
> right mode) channel.
> My board has two of this DACs (left and right channel).
> The control names should be different, hence my
> suggestion for the "Left" and "Right" prefixes.
That's fine and totally normal.
> Another approach would be to say that the machine
> driver is responsible for mixer controls if the devices
> are in mono mode. What do you think?
Yes, the machine driver should do this - you may have left and right on
your board but these configurations are for example often used with 5.1
systems.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-05-05 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 18:13 [RFC PATCH] ASoC: wm8741: Add differential mono mode support Sergej Sawazki
2015-05-04 8:02 ` Charles Keepax
2015-05-04 11:25 ` Mark Brown
2015-05-04 19:03 ` Sergej Sawazki
2015-05-05 11:22 ` Mark Brown
2015-05-05 12:19 ` Sergej Sawazki
2015-05-05 13:57 ` Mark Brown [this message]
2015-05-05 14:07 ` Sergej Sawazki
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=20150505135731.GF22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ce3a@gmx.de \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--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