From: Daniel Ribeiro <drwyrm@gmail.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@kernel.org>
Subject: Re: ASoC: pxa2xx-ssp
Date: Mon, 27 Oct 2008 11:19:34 -0200 [thread overview]
Message-ID: <1225113574.9922.10.camel@brutus> (raw)
In-Reply-To: <20081027124705.GE5896@sirena.org.uk>
Em Seg, 2008-10-27 às 12:47 +0000, Mark Brown escreveu:
> On Sat, Oct 25, 2008 at 03:32:47AM -0200, Daniel Ribeiro wrote:
>
> > To ease your reading, attached is a diff against [0]. It is updated to
> > build on the latest linus tree and handles DAIFMT_I2S and DAIFMT_MSB
> > differently.
>
> Please work against the pxa-ssp driver, not the pxa2xx-ssp driver.
> There are no plans to merge the pxa2xx-ssp driver - the pxa-ssp should
> be able to cover everything, perhaps with a couple of functions selected
> per-CPU, but it's not been tested on pxa2xx yet. It should hopefully be
> making its way upstream today or tomorrow.
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.
Is there anybody using SND_SOC_DAIFMT_I2S with this driver?
I will send you a patch later today. Thanks for the reply! :)
--
Daniel Ribeiro
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-10-27 13:19 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 [this message]
2008-10-27 13:44 ` Mark Brown
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=1225113574.9922.10.camel@brutus \
--to=drwyrm@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox