[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140703133406.2d3e3a1d@armhf>
Date: Thu, 3 Jul 2014 13:34:06 +0200
From: Jean-Francois Moine <moinejf@...e.fr>
To: Mark Brown <broonie@...nel.org>
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, 3 Jul 2014 11:44:32 +0100
Mark Brown <broonie@...nel.org> wrote:
> > > I'd expect this to return an error for the busy DAI rather than just
> > > silently ignore it failing to start or (better) implement some control
> > > to let the user select which of the DAIs is active.
>
> > This is not an error. If the audio subsystem (DPCM, not the user)
> > chooses to activate both I2S and S/PDIF, this means the HDMI audio may
> > be taken either from I2S or from S/PDIF: both inputs have the right
> > format and rate.
>
> 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?
Anyway, the tda998x cannot know if the double route is wanted or not.
--
Ken ar c'hentaƱ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists