linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jsarha@ti.com (Jyri Sarha)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH RFC v3 0/8] Beaglebone-Black HDMI audio
Date: Thu, 30 Jan 2014 14:20:56 +0200	[thread overview]
Message-ID: <52EA43A8.9050909@ti.com> (raw)
In-Reply-To: <20140128102353.48e8fb51@armhf>

On 01/28/2014 11:23 AM, Jean-Francois Moine wrote:
> On Mon, 27 Jan 2014 21:31:59 +0200
> Jyri Sarha <jsarha@ti.com> wrote:
>
>> I would suggest to leave the CTS_N_K to the current setting (3), unless
>> we can change the CTS_N_K on the fly according to the used sample format.
>
> Yes, this is possible:
>
> - the tda998x codec may call the tda998x hdmi in the hw_params()
>    function, i.e. when the sample format is known, and then,
>
> - the tda998x_audio_update() function may have the audio parameters
>    (struct snd_pcm_hw_params) as an argument, and CTS_N_K may be set
>    to either 1, 2 or 3 for SNDRV_PCM_FORMAT_S16_LE / S24_LE and S32_LE.
>
> This is working in my machine. Would it also work for you?
>

I am having trouble getting the tda998x-codec working on BBB. The 
problem is I do not have a DT node for the tda998x driver. Instead I 
have tilcdc-slave node that provides pdata for the tda-driver.

I am thinking of solving the problem by adding a reference to the 
i2c-adapter hosting tda998x as an optional DT property to the codec 
node. I could then dig the driver instance from the i2c adapter's 
children. Any better ideas?

Best regards,
Jyri

  reply	other threads:[~2014-01-30 12:20 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 ` [alsa-devel] [PATCH RFC v3 0/8] Beaglebone-Black HDMI audio Lars-Peter Clausen
2014-01-27 16:17   ` Jyri Sarha
2014-01-27 16:32     ` Lars-Peter Clausen
2014-01-27 19:40       ` Jyri Sarha
2014-01-27 19:47         ` Lars-Peter Clausen
2014-01-27 18:06     ` Jean-Francois Moine
2014-01-27 19:31       ` Jyri Sarha
2014-01-28  9:23         ` Jean-Francois Moine
2014-01-30 12:20           ` Jyri Sarha [this message]
2014-01-30 18:00             ` 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=52EA43A8.9050909@ti.com \
    --to=jsarha@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).