All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Scott Jiang <scott.jiang.linux@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	adi-buildroot-devel@lists.sourceforge.net
Subject: Re: [PATCH] ASoC: blackfin: add bf6xx audio dma driver
Date: Thu, 25 Sep 2014 14:25:41 +0100	[thread overview]
Message-ID: <20140925132541.GR27755@sirena.org.uk> (raw)
In-Reply-To: <CAHG8p1Ad0RbLjdXpjAor8pZXs_9OfUbp142vQ_pc2KReTy9u8w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1299 bytes --]

On Thu, Sep 25, 2014 at 03:24:45PM +0800, Scott Jiang wrote:
> 2014-09-24 19:42 GMT+08:00 Mark Brown <broonie@kernel.org>:

> > These sound more like extended functionality and tweaks rather than
> > massive updates which need a completely separate driver - new modes and
> > so on.

> Yes, it looks similar in i2s mode. But in tdm mode, because we don't need to
> copy 2 channels user buffer to 8 channels dma buffer, it might looks
> very different.
> If you think this patch is not good, I'd send a new one after I merged
> tdm driver.

Well, I'd rather not see the driver split into two separate drivers
again if at all possible - ideally just the bits that need splitting.
It sounds like you need separate copy operations for the two cases but
otherwise things are fairly similar?  If the driver ended up being
nothing but conditional code that'd be bad but if it's just a few places
then it's going to be better to avoid duplicating the entire thing.

> By the way, if the channel order of hardware is different from what is
> expected by alsa,
> the copy work is left to plugin or driver?

If the format is just not something ALSA understands then the driver
ought to do it.  If ALSA does understand it but it's just not what most
applications want then the plugin should be a better choice.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2014-09-25 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24  9:55 [PATCH] ASoC: blackfin: add bf6xx audio dma driver Scott Jiang
2014-09-24  8:26 ` Mark Brown
2014-09-24 10:02   ` Scott Jiang
2014-09-24 11:42     ` Mark Brown
2014-09-25  7:24       ` Scott Jiang
2014-09-25 13:25         ` Mark Brown [this message]

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=20140925132541.GR27755@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=scott.jiang.linux@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 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.