From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Cheng-yi Chiang <cychiang@chromium.org>,
Taniya Das <tdas@codeaurora.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
ALSA development <alsa-devel@alsa-project.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>,
Stephan Gerhold <stephan@gerhold.net>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Patrick Lai <plai@codeaurora.org>, Takashi Iwai <tiwai@suse.com>,
Tzung-Bi Shih <tzungbi@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
Tzung-Bi Shih <tzungbi@google.com>,
Andy Gross <agross@kernel.org>,
Rohit kumar <rohitkr@codeaurora.org>,
Douglas Anderson <dianders@chromium.org>,
Dylan Reid <dgreid@chromium.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Judy Hsiao <judyhsiao@chromium.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ASoC: max98357a: set channels_max to 4
Date: Wed, 16 Jun 2021 21:40:12 +0100 [thread overview]
Message-ID: <20210616204012.GD6418@sirena.org.uk> (raw)
In-Reply-To: <7748e621-ba54-db90-6b56-23e006eb1dbe@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Wed, Jun 16, 2021 at 11:23:36AM -0500, Pierre-Louis Bossart wrote:
> > On this platform there is no TDM support, so there were two I2S data lines.
> Interesting, I haven't seen such 'multi-lane' solutions so far for I2S.
They're moderately common for high end systems (eg, you'll see surround
sound systems do this) - it makes it easier to find higher performance
DACs if you can use regular stereo DACs and it helps a bit with layout
if you can run slower digital signals. There's controllers upstream
that do this without needing to tie together multiple stereo controllers
on the SoC side, one of the variants of the Samsung I2S controllers does
it for example.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-06-16 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 15:47 [PATCH] ASoC: max98357a: set channels_max to 4 Judy Hsiao
2021-06-01 6:20 ` Tzung-Bi Shih
2021-06-15 15:47 ` Cheng-yi Chiang
2021-06-15 16:00 ` Pierre-Louis Bossart
2021-06-16 10:14 ` Cheng-yi Chiang
2021-06-16 16:23 ` Pierre-Louis Bossart
2021-06-16 20:40 ` 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=20210616204012.GD6418@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=cychiang@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=dianders@chromium.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=plai@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=rohitkr@codeaurora.org \
--cc=stephan@gerhold.net \
--cc=swboyd@chromium.org \
--cc=tdas@codeaurora.org \
--cc=tiwai@suse.com \
--cc=tzungbi@chromium.org \
--cc=tzungbi@google.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;
as well as URLs for NNTP newsgroup(s).