All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <philipp.zabel@gmail.com>
To: alsa-devel@alsa-project.org
Cc: Vasily Khoruzhick <anarsoul@gmail.com>,
	Mark Brown <broonie@sirena.org.uk>
Subject: ASoC: UDA1380/I2S/SSP patches
Date: Tue,  3 Feb 2009 17:19:39 +0100	[thread overview]
Message-ID: <1233677983-23710-1-git-send-email-philipp.zabel@gmail.com> (raw)


Right now the snd-soc-magician driver in ASoC dev is severely bitrotted.
I can make it compile and load again, but until now it only outputs silence
(or pops and hisses as I fiddle with the uda1380 registers).
For now, I'd like feedback on these patches in preparation for the magician
update and switch from pxa2xx-ssp to pxa-ssp.

regards
Philipp

             reply	other threads:[~2009-02-03 16:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 16:19 Philipp Zabel [this message]
2009-02-03 16:19 ` [PATCH 1/4] ASoC: uda1380: split set_dai_fmt into _both, _playback and _capture variants Philipp Zabel
2009-02-03 16:41   ` Mark Brown
2009-02-03 16:45     ` pHilipp Zabel
2009-02-04  7:19       ` Vasily Khoruzhick
2009-02-04 13:19         ` Mark Brown
2009-02-03 16:19 ` [PATCH 2/4] ASoC: pxa-ssp: PXA2xx/3xx SSP ports start from 1, not 0 Philipp Zabel
2009-02-03 16:47   ` Mark Brown
2009-02-03 17:13     ` pHilipp Zabel
2009-02-03 17:35       ` Mark Brown
2009-02-03 18:49         ` pHilipp Zabel
2009-02-03 18:56           ` Mark Brown
2009-02-03 16:19 ` [PATCH 3/4] ASoC: pxa2xx-i2s: remove GPIO pin setup Philipp Zabel
2009-02-03 16:32   ` Mark Brown
2009-02-03 16:56     ` pHilipp Zabel
2009-02-03 17:09       ` Mark Brown
2009-02-03 16:19 ` [PATCH 4/4] ASoC: pxa-ssp: select PXA_SSP Philipp Zabel
2009-02-03 16:35   ` Mark Brown
2009-02-03 17:15     ` pHilipp Zabel

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=1233677983-23710-1-git-send-email-philipp.zabel@gmail.com \
    --to=philipp.zabel@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anarsoul@gmail.com \
    --cc=broonie@sirena.org.uk \
    /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.