From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths
Date: Mon, 2 Dec 2013 19:09:13 +0000 [thread overview]
Message-ID: <20131202190913.GQ27568@sirena.org.uk> (raw)
In-Reply-To: <1386007222-10081-1-git-send-email-lee.jones@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
On Mon, Dec 02, 2013 at 06:00:20PM +0000, Lee Jones wrote:
> The Slave Config's addr_width attribute is populated by data_width of
> dma_cfg, which in turn is derived from dma_params' data_size attribute
> and that comes from the slot_width which is always 16 bits (2 Bytes).
> We're cutting out the middle man here and just setting the DMA Slave
> Config directly.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-12-02 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 18:00 Lee Jones
2013-12-02 18:00 ` [PATCH 2/3] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-12-02 18:13 ` [alsa-devel] " Lars-Peter Clausen
2013-12-03 8:36 ` Lee Jones
2013-12-03 8:56 ` Lars-Peter Clausen
2013-12-03 10:03 ` Lee Jones
2013-12-02 18:00 ` [PATCH 3/3] ASoC: ux500: Dynamically fill DAI driver data on probe Lee Jones
2013-12-02 18:10 ` [alsa-devel] " Lars-Peter Clausen
2013-12-03 8:40 ` Lee Jones
2013-12-03 8:57 ` Lars-Peter Clausen
2013-12-03 9:59 ` Lee Jones
2013-12-02 18:34 ` [alsa-devel] [PATCH 1/3] ASoC: ux500_pcm: Stop pretending that we support varying address widths Lars-Peter Clausen
2013-12-03 8:31 ` Lee Jones
2013-12-02 19:09 ` 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=20131202190913.GQ27568@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®