All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Daniel Ribeiro <drwyrm@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@kernel.org>
Subject: Re: ASoC: pxa2xx-ssp
Date: Mon, 27 Oct 2008 13:44:08 +0000	[thread overview]
Message-ID: <20081027134407.GF5896@sirena.org.uk> (raw)
In-Reply-To: <1225113574.9922.10.camel@brutus>

On Mon, Oct 27, 2008 at 11:19:34AM -0200, Daniel Ribeiro wrote:

> 	Ok, i will rebase my work on pxa-ssp.c. But a first look shows that
> pxa_ssp_hw_params sets the ssp frame size depending on the audio stream
> format even for I2S mode. I think it will not work, as I2S needs to
> stick to 32bit frame size.

That's not a general requirement of I2S - many devices are OK with
scaling the number of bit clocks with the data.

> 	Is there anybody using SND_SOC_DAIFMT_I2S with this driver?

I'd go so far as to say that most of the testing has been in I2S mode.
Other modes have been tested but most of the usage is with I2S.

I suspect that what you need to do here to interoperate well with your
codec is to set things up to use TDM so that the extra clocks are
generated by what the CPU believes are idle TDM slots.

> 	I will send you a patch later today. Thanks for the reply! :)

When submitting patches please do try to submit separate patches for
separate logical changes - for example, your previous patch mixed in
changes for recent PXA APIs with changes in the behaviour of the code.

  reply	other threads:[~2008-10-27 13:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24  0:54 ASoC: pxa2xx-ssp Daniel Ribeiro
2008-10-24 15:54 ` Liam Girdwood
2008-10-24 18:14   ` Mark Brown
2008-10-25  5:32   ` Daniel Ribeiro
2008-10-27 12:47     ` Mark Brown
2008-10-27 13:19       ` Daniel Ribeiro
2008-10-27 13:44         ` Mark Brown [this message]
2008-10-30 11:40           ` Daniel Ribeiro
2008-10-30 12:06             ` Mark Brown
2008-10-30 12:24               ` Daniel Ribeiro

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=20081027134407.GF5896@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=drwyrm@gmail.com \
    --cc=lrg@kernel.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 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.