All of lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Hugo Villeneuve <hugo@hugovil.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	alsa-devel@alsa-project.org, Mark Brown <broonie@sirena.org.uk>
Subject: Re: [PATCH 1/1] ASoC: Fix compilation error with davinci-sffsdr module
Date: Thu, 15 Jan 2009 15:37:06 -0700	[thread overview]
Message-ID: <496FBA92.6040907@boundarydevices.com> (raw)
In-Reply-To: <20090115172818.8a216670.hugo@hugovil.com>

Hugo Villeneuve wrote:
> On Thu, 15 Jan 2009 15:10:01 -0700
> Troy Kisky <troy.kisky@boundarydevices.com> wrote:
> 
>>> Hopefully a comparison of the mainline and DaVinci trees will show
>>> something...
>> In davinci-sffsdr.c I see
>>
>> 	ret = snd_soc_dai_set_fmt(cpu_dai,
>> 				  SND_SOC_DAIFMT_RIGHT_J |
>> 				  SND_SOC_DAIFMT_CBM_CFS |
>> 				  SND_SOC_DAIFMT_IB_NF);
>>
>> When I changed the evm board flags passed, I didn't change this file.
>> So, you'll need something like
>>
>> 	ret = snd_soc_dai_set_fmt(cpu_dai,
>> 				  SND_SOC_DAIFMT_DSP_A |
>> 				  SND_SOC_DAIFMT_CBM_CFS |
>> 				  SND_SOC_DAIFMT_NB_NF);
> 
> I´m not using the same codec as on the EVM.

I know your not using the AIC33, but if your using davinci-i2s, then
the change will affect you.

> I´m using the PCM3008 and I
> need to use the right-justified mode and the SND_SOC_DAIFMT_IB_NF flag
> for it to work (it used to work a few weeks/months ago).

Davinci does not support a general right justified mode. But DSP_A may
be close enough. Especially if it worked before.

>  
>> But, you should be seeing error messages.
> 
> Did someone test the latest git tree and audio on a DM644x EVM to see if
> it still works?

I don't have an evm, but our custom board works fine.


Troy

  reply	other threads:[~2009-01-15 22:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 21:23 [PATCH 1/1] ASoC: Fix compilation error with davinci-sffsdr module Hugo Villeneuve
2009-01-06 21:31 ` Mark Brown
2009-01-06 21:41   ` Hugo Villeneuve
2009-01-06 22:00     ` Mark Brown
2009-01-14 20:54       ` Hugo Villeneuve
2009-01-15 11:18         ` Mark Brown
2009-01-15 19:54           ` Hugo Villeneuve
2009-01-15 20:01             ` Mark Brown
2009-01-15 20:10               ` Hugo Villeneuve
2009-01-15 22:10               ` Troy Kisky
2009-01-15 22:28                 ` Hugo Villeneuve
2009-01-15 22:37                   ` Troy Kisky [this message]
2009-01-15 22:37                   ` David Brownell
2009-01-15 22:50                   ` Troy Kisky
2009-01-16 17:05                     ` Hugo Villeneuve

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=496FBA92.6040907@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=hugo@hugovil.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 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.