All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Jiang <scott.jiang.linux@gmail.com>
To: Mark Brown <broonie@kernel.org>
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 15:24:45 +0800	[thread overview]
Message-ID: <CAHG8p1Ad0RbLjdXpjAor8pZXs_9OfUbp142vQ_pc2KReTy9u8w@mail.gmail.com> (raw)
In-Reply-To: <20140924114232.GI16977@sirena.org.uk>

2014-09-24 19:42 GMT+08:00 Mark Brown <broonie@kernel.org>:
> On Wed, Sep 24, 2014 at 06:02:40PM +0800, Scott Jiang wrote:
>> 2014-09-24 16:26 GMT+08:00 Mark Brown <broonie@kernel.org>:
>
>> > Can you go into a bit more detail on the differences - clearly there's
>> > some similarlities since the drivers got merged, can we really not share
>> > any code?
>
>> First, sport2 only supports i2s and left justified mode, while sport3
>> adds i2s packed
>> and right justified mode. Second, in tdm mode for sport2, tx and rx
>> are dependent and have
>> a window granularity of 8 channel. While sport3 doesn't have these
>> limits. What's more,
>> sport3 is not only used on blackfin. That means many patches can only
>> apply to this driver.
>
> 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.
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?

Scott

  reply	other threads:[~2014-09-25  7:24 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 [this message]
2014-09-25 13:25         ` 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=CAHG8p1Ad0RbLjdXpjAor8pZXs_9OfUbp142vQ_pc2KReTy9u8w@mail.gmail.com \
    --to=scott.jiang.linux@gmail.com \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@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 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.