linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: detheridge@ti.com, alsa-devel@alsa-project.org,
	Jean-Francois Moine <moinejf@free.fr>,
	dri-devel@lists.freedesktop.org, peter.ujfalusi@ti.com,
	broonie@kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC v3 0/8] Beaglebone-Black HDMI audio
Date: Mon, 27 Jan 2014 18:17:54 +0200	[thread overview]
Message-ID: <52E686B2.9060806@ti.com> (raw)
In-Reply-To: <52E6806A.2090109@metafoo.de>

On 01/27/2014 05:51 PM, Lars-Peter Clausen wrote:
> Hi,
>
> I think you should try to get this in sync with the work Jean-Francois is
> currently doing[1]. Having the HDMI transmitter register a CODEC device is
> definitely the right approach, compared to the rather 'interesting'
> constraints stuff you do in patch 4.
>

Oh, Jean-Francois's patches are now out. I'll take those into use, but I 
am afraid it still does not save me from the constraint stuff.

The most complex piece of code comes from limited sample-rate 
availability, which is coming Beaglebone-Black desing (available i2s 
master clock), not from the HDMI encoder itself. It does not help with 
the stereo only limitation either, because it comes from the one wire 
only audio data connection on BBB.

Support for S16_LE could maybe be added if the tda998x specific codec 
would fiddle with CTS_N predivider-setting (K select) according to the 
used sample width. But it appears Cobox plays all the sample formats 
fine without this change, so the question is if playing around with 
CTS_N predivider would break already working support there (something to 
be tested).


Best regards,
Jyri

  reply	other threads:[~2014-01-27 16:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 15:37 [PATCH RFC v3 0/8] Beaglebone-Black HDMI audio Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 1/8] clk: add gpio controlled clock Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 2/8] ASoC: davinci-evm: Add named clock reference to DT bindings Jyri Sarha
2014-01-27 18:10   ` Mark Brown
2014-01-27 15:37 ` [PATCH RFC v3 3/8] ASoC: davinci-mcasp: Set BCLK divider if McASP is BCLK master Jyri Sarha
2014-01-27 20:46   ` Mark Brown
2014-01-27 15:37 ` [PATCH RFC v3 4/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus Jyri Sarha
2014-01-27 20:49   ` Mark Brown
2014-01-28  7:47     ` Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 5/8] ASoC: davinci: HDMI audio build for AM33XX and TDA998x Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 6/8] drm/tilcdc: Add I2C HDMI audio config for tda998x Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 7/8] ARM: OMAP2+: omap2plus_defconfig: Enable tilcdc and TDA998X HDMI support Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 8/8] ARM: OMAP2+: omap2plus_defconfig: Enable BeagleBone Black HDMI audio support Jyri Sarha
2014-01-27 15:51 ` [PATCH RFC v3 0/8] Beaglebone-Black HDMI audio Lars-Peter Clausen
2014-01-27 16:17   ` Jyri Sarha [this message]
2014-01-27 16:32     ` [alsa-devel] " Lars-Peter Clausen
2014-01-27 19:40       ` Jyri Sarha
2014-01-27 19:47         ` [alsa-devel] " Lars-Peter Clausen
2014-01-27 18:06     ` Jean-Francois Moine
2014-01-27 19:31       ` Jyri Sarha
2014-01-28  9:23         ` [alsa-devel] " Jean-Francois Moine
2014-01-30 12:20           ` Jyri Sarha
2014-01-30 18:00             ` [alsa-devel] " 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=52E686B2.9060806@ti.com \
    --to=jsarha@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=detheridge@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=peter.ujfalusi@ti.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).