All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alexander <subaparts@yandex.ru>
Cc: alsa-devel@alsa-project.org, ryan@bluewatersys.com,
	linux-arm-kernel@lists.infradead.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH] ASoC: EP93xx: fixed LRCLK rate and DMA oper. in I2S code
Date: Mon, 17 Jan 2011 14:07:34 +0000	[thread overview]
Message-ID: <20110117140734.GG21113@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1295182085.15631.231.camel@r60e>

On Sun, Jan 16, 2011 at 03:48:05PM +0300, Alexander wrote:
> From: Alexander Sverdlin <subaparts@yandex.ru>
> 
> Changelog:
> 1. I2S module of EP93xx should be feed by 32bit DMA transfers. This is 
> hardware limitation and that's the way original Cirrus's driver worked.

Applied, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: EP93xx: fixed LRCLK rate and DMA oper. in I2S code
Date: Mon, 17 Jan 2011 14:07:34 +0000	[thread overview]
Message-ID: <20110117140734.GG21113@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1295182085.15631.231.camel@r60e>

On Sun, Jan 16, 2011 at 03:48:05PM +0300, Alexander wrote:
> From: Alexander Sverdlin <subaparts@yandex.ru>
> 
> Changelog:
> 1. I2S module of EP93xx should be feed by 32bit DMA transfers. This is 
> hardware limitation and that's the way original Cirrus's driver worked.

Applied, thanks.

  parent reply	other threads:[~2011-01-17 14:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 12:01 [PATCH 1/3] ASoC: EP93xx I2S and PCM fixes Alexander
2010-12-08 12:01 ` Alexander
2010-12-08 12:46 ` Mark Brown
2010-12-08 12:46   ` Mark Brown
2010-12-09  0:37   ` Alexander
2010-12-09  0:37     ` Alexander
2010-12-09 10:54     ` Mark Brown
2010-12-09 10:54       ` Mark Brown
2010-12-09 12:17       ` Alexander
2010-12-09 12:17         ` Alexander
2010-12-09 12:34         ` Mark Brown
2010-12-09 12:34           ` Mark Brown
2010-12-09 21:14           ` Alexander
2010-12-09 21:14             ` Alexander
2010-12-10 15:07             ` Mark Brown
2010-12-10 15:07               ` Mark Brown
2011-01-16 11:21               ` Alexander
2011-01-16 11:21                 ` Alexander
2011-01-16 11:27                 ` Mark Brown
2011-01-16 11:27                   ` Mark Brown
2010-12-09  0:43   ` [PATCH] ASoC: EP93xx: sampling rate range extended Alexander
2010-12-09  0:43     ` Alexander
2010-12-09 10:07     ` Liam Girdwood
2010-12-09 10:07       ` [alsa-devel] " Liam Girdwood
2010-12-09 11:10     ` Mark Brown
2010-12-09 11:10       ` Mark Brown
2010-12-09  0:59   ` [PATCH] ASoC: EP93xx: fixed LRCLK rate and DMA oper. in I2S code Alexander
2010-12-09  0:59     ` Alexander
2010-12-09 10:08     ` Liam Girdwood
2010-12-09 10:08       ` [alsa-devel] " Liam Girdwood
2011-01-16 12:48   ` Alexander
2011-01-16 12:48     ` Alexander
2011-01-17 14:05     ` Liam Girdwood
2011-01-17 14:05       ` [alsa-devel] " Liam Girdwood
2011-01-17 14:07     ` Mark Brown [this message]
2011-01-17 14:07       ` 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=20110117140734.GG21113@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=ryan@bluewatersys.com \
    --cc=subaparts@yandex.ru \
    /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.