[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140703115924.GY410@sirena.org.uk>
Date: Thu, 3 Jul 2014 12:59:24 +0100
From: Mark Brown <broonie@...nel.org>
To: Jean-Francois Moine <moinejf@...e.fr>
Cc: Andrew Lunn <andrew@...n.ch>,
Russell King - ARM Linux <linux@....linux.org.uk>,
devicetree@...r.kernel.org, alsa-devel@...a-project.org,
lgirdwood@...il.com, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, Rob Clark <robdclark@...il.com>,
Dave Airlie <airlied@...il.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
On Thu, Jul 03, 2014 at 01:34:06PM +0200, Jean-Francois Moine wrote:
> Mark Brown <broonie@...nel.org> wrote:
> > Your board happens to only be able to present the same input on both I2S
> > and S/PDIF but that might not apply to other boards, they may be able to
> > route different signals to each which would present a practical problem.
> If there are two different streamss on I2S and S/PDIF, and if the audio
> subsystem wants to route these streams to the same connector (widget
> 'hdmi-out'), then, somewhere, there should be a software or a design
> bug. No?
Yes, which is why the driver shouldn't silently ignore the situation.
> Anyway, the tda998x cannot know if the double route is wanted or not.
It doesn't need to know, it just needs to identify something it can't
support either by providing a way to pick which interface is used or by
rejecting the second interface.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists