public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Paul Shen <boshen9@gmail.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	Eric Miao <eric.y.miao@gmail.com>,
	Philipp Zabel <philipp.zabel@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	Daniel Ribeiro <drwyrm@gmail.com>
Subject: Re: [PATCH 1/3] ASoC: change set_tdm_slot api to allow slot_width	override.
Date: Wed, 5 Aug 2009 01:42:17 +0200	[thread overview]
Message-ID: <20090804234217.GX19257@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090804205545.GB29518@sirena.org.uk>

On Tue, Aug 04, 2009 at 09:55:45PM +0100, Mark Brown wrote:
> On Mon, Jun 15, 2009 at 09:44:31PM -0300, Daniel Ribeiro wrote:
> > Extend set_tdm_slot to allow the user to arbitrarily set the frame width
> > and active TX/RX slots.
> 
> > Updates magician.c and wm9081.c for the new set_tdm_slot(). wm9081.c
> > still doesn't handle the slot_width override.
> 
> > While being there, correct an incorrect use of SlotsPerFrm(7) use in
> > bitmask on pxa-ssp.c (SSCR0_SlotsPerFrm(x) is (((x) - 1) << 24)) ).
> 
> > (this series is meant for Mark's for-2.6.32 branch)
> 
> > Signed-off-by: Daniel Ribeiro <drwyrm@gmail.com>
> 
> So.  These have been sitting for quite some time now.  Unfortunately I
> went on holiday immediately after it was last submitted my Zylonite
> system has been bricked for pretty much all of the time since then so
> I've been remiss in following up.  Sorry about that, my bad.
> 
> My inclination here is to apply these changes - they look like a clear
> win for pretty much every machine except Daniel Mack's out of tree
> system which needs the 64 bit TDM slots.  It's a shame to break that but
> there seems to be such a clear advantage from the changes, especially
> the new set_tdm_slot() API, that it seems like a win overall.  I've got
> a feeling that the fix for that system may have to be allowing the
> machine driver to rewrite the hw_params for the CPU driver to lie about
> the data format.

Hmm. I like to stress that I appreciate the efford taken to clean up all
the API around this, and I would like to give my 'tested-by' on the
patches.

However, if it is about cleaning up things properly, we should make sure
the system does what it's been told to do, and with Daniel Ribeiro's
patches, it unfortunately doesn't yet. I'm only blaming the utterly
broken PXA register set for that, but that should be fixed before the
whole series goes in. And I'm quite sure I'm not the only user of 64 bit
TDM slots, even though I might be the only one having discussed that.

Daniel, could you resend the latest version of your patches? I hope to
find some time to again test them, find the differences in the register
bits and amend them in a way that they actually do what is needed for my
system.

And btw - the code for the system I'm working on will be release
eventually, of course, and hopefully even be merged mainline. 

Thanks,
Daniel

  reply	other threads:[~2009-08-04 23:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  0:44 [PATCH 1/3] ASoC: change set_tdm_slot api to allow slot_width override Daniel Ribeiro
2009-06-16 10:28 ` pHilipp Zabel
2009-08-04 20:55 ` Mark Brown
2009-08-04 23:42   ` Daniel Mack [this message]
2009-08-05 16:47     ` mixing audio waves for analysis! Guilherme Longo
2009-08-06 14:36   ` [PATCH 1/3] ASoC: change set_tdm_slot api to allow slot_width override Eric Miao
2009-08-06 15:01     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2009-08-06 14:55 Mark Brown
2009-08-06 14:59 ` Daniel Mack
2009-08-11 12:04 ` Mark Brown

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=20090804234217.GX19257@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=boshen9@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=drwyrm@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=philipp.zabel@gmail.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