From: Jean-Francois Moine <moinejf@free.fr>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
alsa-devel@alsa-project.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, lgirdwood@gmail.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 13:34:06 +0200 [thread overview]
Message-ID: <20140703133406.2d3e3a1d@armhf> (raw)
In-Reply-To: <20140703104432.GV410@sirena.org.uk>
On Thu, 3 Jul 2014 11:44:32 +0100
Mark Brown <broonie@kernel.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/
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 13:34:06 +0200 [thread overview]
Message-ID: <20140703133406.2d3e3a1d@armhf> (raw)
In-Reply-To: <20140703104432.GV410@sirena.org.uk>
On Thu, 3 Jul 2014 11:44:32 +0100
Mark Brown <broonie@kernel.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/
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
lgirdwood@gmail.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Rob Clark <robdclark@gmail.com>,
Dave Airlie <airlied@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 13:34:06 +0200 [thread overview]
Message-ID: <20140703133406.2d3e3a1d@armhf> (raw)
In-Reply-To: <20140703104432.GV410@sirena.org.uk>
On Thu, 3 Jul 2014 11:44:32 +0100
Mark Brown <broonie@kernel.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/
next prev parent reply other threads:[~2014-07-03 11:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 16:38 [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter Jean-Francois Moine
2014-07-02 16:38 ` Jean-Francois Moine
2014-07-02 16:38 ` Jean-Francois Moine
2014-07-02 16:56 ` Andrew Lunn
2014-07-02 16:56 ` Andrew Lunn
2014-07-02 17:51 ` Jean-Francois Moine
2014-07-02 17:51 ` Jean-Francois Moine
2014-07-02 17:51 ` Jean-Francois Moine
2014-07-02 18:02 ` Russell King - ARM Linux
2014-07-02 18:02 ` Russell King - ARM Linux
2014-07-02 18:02 ` Russell King - ARM Linux
2014-07-02 19:37 ` Mark Brown
2014-07-02 19:37 ` Mark Brown
2014-07-02 19:42 ` Mark Brown
2014-07-02 19:42 ` Mark Brown
2014-07-03 5:49 ` Jean-Francois Moine
2014-07-03 5:49 ` Jean-Francois Moine
2014-07-03 5:49 ` Jean-Francois Moine
2014-07-03 10:44 ` Mark Brown
2014-07-03 10:44 ` Mark Brown
2014-07-03 10:44 ` Mark Brown
2014-07-03 11:34 ` Jean-Francois Moine [this message]
2014-07-03 11:34 ` Jean-Francois Moine
2014-07-03 11:34 ` Jean-Francois Moine
2014-07-03 11:59 ` Mark Brown
2014-07-03 11:59 ` Mark Brown
2014-07-03 11:59 ` Mark Brown
2014-07-03 13:28 ` Jean-Francois Moine
2014-07-03 13:28 ` Jean-Francois Moine
2014-07-03 13:28 ` Jean-Francois Moine
2014-07-03 13:43 ` Russell King - ARM Linux
2014-07-03 13:43 ` Russell King - ARM Linux
2014-07-03 13:43 ` Russell King - ARM Linux
[not found] ` <20140703134346.GW32514-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-07-03 15:29 ` Jean-Francois Moine
2014-07-03 15:29 ` Jean-Francois Moine
2014-07-03 15:29 ` Jean-Francois Moine
2014-07-03 15:43 ` Russell King - ARM Linux
2014-07-03 15:43 ` Russell King - ARM Linux
2014-07-03 15:43 ` Russell King - ARM Linux
2014-07-03 16:26 ` Jean-Francois Moine
2014-07-03 16:26 ` Jean-Francois Moine
2014-07-03 16:26 ` Jean-Francois Moine
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=20140703133406.2d3e3a1d@armhf \
--to=moinejf@free.fr \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.