From: Nicolin Chen <b42378@freescale.com>
To: s.hauer@pengutronix.de, timur@tabi.org, shawn.guo@linaro.org,
broonie@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
alsa-devel@alsa-project.org, rob.herring@calxeda.com,
mark.rutland@arm.com, swarren@wwwdotorg.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org
Subject: [PATCH v2 0/4] Add dual-fifo mode support of i.MX ssi
Date: Thu, 31 Oct 2013 14:32:02 +0800 [thread overview]
Message-ID: <cover.1383197521.git.b42378@freescale.com> (raw)
Changelog
v2:
* Instead of adding rogue scripts to current SDMA driver based on firmware
* V1, we define the new SDMA firmware as version 2 and bisect the PATCH-1
* to two patches: The first is to add version check code to the SDMA driver;
* And the second is to add SSI dual FIFO DMATYPE.
*
* Nothing changes for the last two patches.
v1:
* SSI can reduce hardware overrun/underrun possibility when using dual
* fifo mode. To support this mode, we need to first update sdma sciprt
* list, and then enable dual fifo BIT in SSI driver, and last update DT
* bindings of i.MX series.
*
* ! This series of patches has a direct dependency between them. When
* ! applying them, we need to apply in one single branch. Otherwise,
* ! it would break currect branches.
Nicolin Chen (4):
dma: imx-sdma: Add sdma firmware version 2 support
dma: imx-sdma: Add new dma type for ssi dual fifo script
ASoC: fsl_ssi: Add dual fifo mode support
ARM: dts: imx: use dual-fifo sdma script for ssi
.../devicetree/bindings/dma/fsl-imx-sdma.txt | 1 +
arch/arm/boot/dts/imx51.dtsi | 4 ++--
arch/arm/boot/dts/imx53.dtsi | 4 ++--
arch/arm/boot/dts/imx6qdl.dtsi | 12 +++++------
arch/arm/boot/dts/imx6sl.dtsi | 12 +++++------
drivers/dma/imx-sdma.c | 19 ++++++++++++++++-
include/linux/platform_data/dma-imx-sdma.h | 3 +++
include/linux/platform_data/dma-imx.h | 1 +
sound/soc/fsl/fsl_ssi.c | 24 +++++++++++++++++++++-
9 files changed, 62 insertions(+), 18 deletions(-)
--
1.8.4
next reply other threads:[~2013-10-31 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 6:32 Nicolin Chen [this message]
[not found] ` <cover.1383197521.git.b42378-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-10-31 6:32 ` [PATCH v2 1/4] dma: imx-sdma: Add sdma firmware version 2 support Nicolin Chen
2013-10-31 7:29 ` Sascha Hauer
2013-10-31 6:32 ` [PATCH v2 4/4] ARM: dts: imx: use dual-fifo sdma script for ssi Nicolin Chen
2013-10-31 6:32 ` [PATCH v2 2/4] dma: imx-sdma: Add new dma type for ssi dual fifo script Nicolin Chen
2013-10-31 6:32 ` [PATCH v2 3/4] ASoC: fsl_ssi: Add dual fifo mode support Nicolin Chen
2013-10-31 7:54 ` Philippe Rétornaz
2013-10-31 7:44 ` Nicolin Chen
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=cover.1383197521.git.b42378@freescale.com \
--to=b42378@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=timur@tabi.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).