All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org, kgene.kim@samsung.com,
	Jassi Brar <jassi.brar@samsung.com>,
	ben-linux@fluff.org, june.bae@samsung.com, lrg@slimlogic.co.uk,
	sw.youn@samsung.com
Subject: Re: [PATCH 00/25] ASoC: Overhaul Samsung drivers
Date: Tue, 19 Oct 2010 02:56:02 -0700	[thread overview]
Message-ID: <20101019095602.GA12173@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1287471805-17952-1-git-send-email-jassisinghbrar@gmail.com>

On Tue, Oct 19, 2010 at 04:03:25PM +0900, Jassi Brar wrote:

>   Simple testing of 5.1 channel and hardware mixing seems to work (though
> there seems to be some issue with symmetric_rates in soc-core.c which
> would be tried to fix later as saperate issue).

symmetric_rates can only cope with straight through DAIs.  It'd need a
substantial overhaul to be able to be told about multiple DAIs all
needing to share the same link.  We need to do something about this
anyway for multi-drop DAI links, provide some way of saying that
multiple DAI links share clocks and need to have their configurations
kept in lockstep.

  parent reply	other threads:[~2010-10-19  9:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19  7:03 [PATCH 00/25] ASoC: Overhaul Samsung drivers Jassi Brar
2010-10-19  7:30 ` Kukjin Kim
2010-10-19  7:30   ` Kukjin Kim
2010-10-19  8:00   ` Vasily khoruzhick
2010-10-19  8:00     ` [alsa-devel] " Vasily khoruzhick
2010-10-19  8:52     ` Mark Brown
2010-10-19  8:52       ` [alsa-devel] " Mark Brown
2010-10-19  9:56 ` Mark Brown [this message]
2010-10-22  4:59 ` Mark Brown
2010-10-22  5:13   ` Kukjin Kim
     [not found] <1287473432-19408-1-git-send-email-jassi.brar@samsung.com>
2010-10-21 16:55 ` Maurus Cuelenaere
2010-10-21 16:55   ` Maurus Cuelenaere
2010-10-21 20:56   ` Jassi Brar

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=20101019095602.GA12173@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ben-linux@fluff.org \
    --cc=jassi.brar@samsung.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=june.bae@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=sw.youn@samsung.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.