From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/10] ASoC: dma: ARM: ux500: Obtain DMA data from Device Tree
Date: Tue, 19 Nov 2013 11:07:39 +0000 [thread overview]
Message-ID: <1384859269-19801-1-git-send-email-lee.jones@linaro.org> (raw)
At this moment in time the Ux500 ASoC driver obtains its DMA information
via AUXDATA platform data passing. To make the driver more independent
we have to start extracting it from the Device Tree.
If this patch-set could go through ASoC as a whole, it would drive down
the chance of a dependency mess. Vinod has already provided Acks for his
parts, so it's just between you two Linus and Mark.
Documentation/devicetree/bindings/dma/ste-dma40.txt | 3 ++
arch/arm/boot/dts/ste-dbx5x0.dtsi | 15 ++++++++++
arch/arm/mach-ux500/board-mop500-audio.c | 8 +++---
drivers/dma/ste_dma40.c | 4 +++
include/linux/platform_data/asoc-ux500-msp.h | 9 +-----
sound/soc/ux500/mop500.c | 2 ++
sound/soc/ux500/ux500_msp_dai.c | 150 +++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------
sound/soc/ux500/ux500_msp_i2s.c | 56 +++++++++++++++++++++++++++----------
sound/soc/ux500/ux500_msp_i2s.h | 2 +-
sound/soc/ux500/ux500_pcm.c | 32 +++++++++++++++------
10 files changed, 160 insertions(+), 121 deletions(-)
Cc: Mark Brown <broonie@kernel.org>
next reply other threads:[~2013-11-19 11:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 11:07 Lee Jones [this message]
2013-11-19 11:07 ` [PATCH 01/10] dma: ste_dma40: Expand DT binding to accept 'high-priority channel' flag Lee Jones
2013-11-19 21:02 ` Linus Walleij
2013-11-19 11:07 ` [PATCH 02/10] dma: ste_dma40: Parse flags property for new 'high priority channel' request Lee Jones
2013-11-19 21:03 ` Linus Walleij
2013-11-19 11:07 ` [PATCH 03/10] ARM: ux500: Don't use enums for MSP IDs - for easy DT conversion Lee Jones
2013-11-19 11:07 ` [PATCH 04/10] ARM: ux500: Add DMA config bindings for MSP devices Lee Jones
2013-11-19 21:06 ` Linus Walleij
2013-11-19 11:07 ` [PATCH 05/10] ASoC: Ux500: Match platform by device node when booting Device Tree Lee Jones
2013-11-19 18:49 ` Mark Brown
2013-11-19 11:07 ` [PATCH 06/10] ASoC: ux500_pcm: Extend Device Tree support to deal with DMA data Lee Jones
2013-11-19 18:50 ` Mark Brown
2013-11-19 11:07 ` [PATCH 07/10] ASoC: ux500: Store DMA data in the DAI differently in the pdata and DT case Lee Jones
2013-11-19 18:51 ` Mark Brown
2013-12-02 7:35 ` [alsa-devel] " Olof Johansson
2013-12-02 10:12 ` Lee Jones
2013-12-02 13:54 ` Mark Brown
2013-12-02 14:03 ` Lee Jones
2013-12-02 14:04 ` Mark Brown
2013-12-04 17:45 ` Kevin Hilman
2013-12-04 18:03 ` Lee Jones
2013-11-19 11:07 ` [PATCH 08/10] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-11-19 18:48 ` Mark Brown
2013-11-19 19:33 ` Lee Jones
2013-11-19 19:40 ` Lars-Peter Clausen
2013-11-19 20:09 ` Mark Brown
2013-11-19 11:07 ` [PATCH 09/10] ASoC: ux500_pcm: Take out pointless dev_dbg() call Lee Jones
2013-11-19 18:51 ` Mark Brown
2013-11-19 11:07 ` [PATCH 10/10] ASoC: ux500: Dynamically fill DAI driver data on probe Lee Jones
2013-11-19 18:53 ` [PATCH 00/10] ASoC: dma: ARM: ux500: Obtain DMA data from Device Tree Mark Brown
2013-11-29 16:03 ` Lee Jones
2013-11-29 16:42 ` Mark Brown
2013-11-29 17:37 ` Lee Jones
2013-11-29 18:21 ` 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=1384859269-19801-1-git-send-email-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).