From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH 2/2] ASoC: meson: add t9015 internal DAC driver
Date: Wed, 19 Feb 2020 15:44:25 +0000 [thread overview]
Message-ID: <20200219154425.GD4488@sirena.org.uk> (raw)
In-Reply-To: <1ja75ey4vj.fsf@starbuckisacylon.baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Wed, Feb 19, 2020 at 04:27:12PM +0100, Jerome Brunet wrote:
> On Wed 19 Feb 2020 at 15:55, Mark Brown <broonie@kernel.org> wrote:
> >> + /* Channel Src */
> >> + SOC_ENUM("Right DAC Source", dacr_in_enum),
> >> + SOC_ENUM("Left DAC Source", dacl_in_enum),
> > Ideally these would be moved into DAPM (using an AIF_IN widget for the
> > DAI).
> I can (I initially did) but I don't think it is worth it.
> I would split Playback into 2 AIF for Left and Right, then add a mux to
> select one them if front of both DAC. It will had 4 widgets and 6 routes
> but it won't allow turn anything on or off. There is no PM improvement.
> Do you still want me to change this ?
It can help us track things like external amps connected to the DACs,
especially when we manage to get to the point of tracking individual
audio streams over DAI links.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-02-19 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 13:36 [PATCH 0/2] ASoC: meson: add internal DAC support Jerome Brunet
2020-02-19 13:36 ` [PATCH 1/2] ASoC: meson: add t9015 internal codec binding documentation Jerome Brunet
2020-02-19 13:36 ` [PATCH 2/2] ASoC: meson: add t9015 internal DAC driver Jerome Brunet
2020-02-19 14:55 ` Mark Brown
2020-02-19 15:27 ` Jerome Brunet
2020-02-19 15:44 ` Mark Brown [this message]
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=20200219154425.GD4488@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).