From: Mark Brown <broonie@kernel.org>
To: Jun Nie <jun.nie@linaro.org>
Cc: alsa-devel@alsa-project.org, Shawn Guo <shawn.guo@linaro.org>,
"wan.zhijun" <wan.zhijun@zte.com.cn>,
Liam Girdwood <lgirdwood@gmail.com>,
ZTE-LT Mailman List <zte-lt@lists.linaro.org>
Subject: Re: [PATCH 2/2] ASoC: zx: Add zx296702 SPDIF support
Date: Tue, 5 May 2015 23:07:17 +0100 [thread overview]
Message-ID: <20150505220717.GI15510@sirena.org.uk> (raw)
In-Reply-To: <CABymUCNYZ=ik9Z6zfOXzFN6GyfQ+Z98EArPuG-s1e2S01rvU-w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1420 bytes --]
On Tue, May 05, 2015 at 09:43:56AM +0800, Jun Nie wrote:
> 2015-05-04 21:54 GMT+08:00 Mark Brown <broonie@kernel.org>:
> > So this special HDMI S/PDIF controller is directly integrated with the
> > HDMI IP in the SoC and not usable as a generic S/PDIF controller? That
> > seems to mirror system designs which have an external HDMI encoder which
> > use S/PDIF or I2S to connect the audio portion to an external device.
> The first SPDIF controller on ZTE SOC is dedicated for HDMI and the
> 2nd one is for external output only via physical pad. The two
> controller IPs are identical, also independent with each other and
> HDMI in register address region.
OK, so this does sound like the software should like one of the systems
with an external HDMI encoder and the HDMI handled separately rather
than in this driver anyway.
> > I'd suggest for future versions reorganizing things so that you add the
> > S/PDIF driver with only S/PDIF support and then have a separate patch
> > that layers on the HDMI support.
> Reasonable suggestion. Then I can have more time to think about HDMI
> part. More comments is welcome if any.
This sounds like the software should look like a TDA998x (which is
having patches posted still) so just have the S/PDIF controllers as pure
S/PDIF controllers and then a separate driver for the HDMI part that
it's hooked up to which deals with the audio configuration for the HDMI
side.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-05-05 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430366850-10281-1-git-send-email-jun.nie@linaro.org>
[not found] ` <1430366850-10281-2-git-send-email-jun.nie@linaro.org>
2015-05-01 10:55 ` [PATCH 2/2] ASoC: zx: Add zx296702 SPDIF support Mark Brown
[not found] ` <CABymUCNcD_7fxCh110A-w5=3Lo5Jn2aCHGy3DwLDroZP9oqi4w@mail.gmail.com>
2015-05-04 13:54 ` Mark Brown
[not found] ` <CABymUCNYZ=ik9Z6zfOXzFN6GyfQ+Z98EArPuG-s1e2S01rvU-w@mail.gmail.com>
2015-05-05 22:07 ` Mark Brown [this message]
2015-05-01 11:17 ` [PATCH 1/2] ASoC: zx: Add ZTE zx296702 pcm support 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=20150505220717.GI15510@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jun.nie@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=wan.zhijun@zte.com.cn \
--cc=zte-lt@lists.linaro.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