From: Shawn Guo <shawn.guo@linaro.org>
To: Huang Shijie <b32955@freescale.com>
Cc: vinod.koul@intel.com, artem.bityutskiy@intel.com,
shijie8@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-mtd@lists.infradead.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, w.sang@pengutronix.de,
LW@KARO-electronics.de, alsa-devel@alsa-project.org,
b29396@freescale.com
Subject: Re: [PATCH 00/10] patch set about the MXS-DMA
Date: Thu, 19 Jan 2012 17:10:37 +0800 [thread overview]
Message-ID: <20120119091034.GH2247@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1326953767-24155-1-git-send-email-b32955@freescale.com>
On Thu, Jan 19, 2012 at 02:15:57PM +0800, Huang Shijie wrote:
> This patch set does two things about the MXS-DMA:
> [1] patch 1 ~ patch 5: move the mxs dma header to a more common place.
> Beside the mx23/mx28, the APBH-DMA is also used by MX50 and MX6Q.
> So move the mxs dma header file to a more common place, and rename
> it to mxs-dma.h
>
For the sake of bitsec, these 5 patches need to be one.
> [2] patch 6 ~ patch 10: rewrite the last parameter of mxs_dma_prep_slave_sg().
For the sake of bitsec, at least patches #7 and #8 need to be one patch.
That said, if I apply the series and then check out the commit at patch
#7, you need to all mxs-dma client drivers, mxs-mmc, gpmi do not break.
> In the new GPMI version, some hardware behavior changes.
> The WAIT4END bit should be set in the middle one of the ECC READ page DMA chain.
> The DMA chain should be set like this:
>
> +-----+ +-----+ +-----+
> | cmd | ------------> | cmd | ------------------> | cmd |
> +-----+ +-----+ +-----+
> ^ ^
> | |
> | |
> set WAIT4END here too set WAIT4END here
>
> Please read the comment in patch "MXS-DMA : add more flags for MXS-DMA".
>
> Huang Shijie (10):
> MXS-DMA : move the mxs-dma.h to a more common place
> MXS-DMA : change the header
> MXS-MMC : change the DMA header file
> MTD/GPMI : change the DMA header file
> ASoc : change the DMA header file
> MXS-DMA : add more flags for MXS-DMA
> MXS-DMA : change the last parameter of mxs_dma_prep_slave_sg()
> MXS-MMC : use the new DMA flags
> MTD/GPMI : add a new field `gpmi_version`
> MTD/GPMI : change the code for new DMA interface
>
Please try to make these subject prefix consistent with the existing
ones in the tree. You can get them from 'git log' output. For example
"mxs-dma: ..." is better than "MXS-DMA : ...".
--
Regards,
Shawn
next prev parent reply other threads:[~2012-01-19 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 6:15 [PATCH 00/10] patch set about the MXS-DMA Huang Shijie
2012-01-19 6:15 ` [PATCH 01/10] MXS-DMA : move the mxs-dma.h to a more common place Huang Shijie
2012-01-19 8:58 ` Wolfram Sang
2012-01-19 11:20 ` Mark Brown
2012-01-19 13:04 ` Shawn Guo
2012-01-19 6:15 ` [PATCH 02/10] MXS-DMA : change the header Huang Shijie
2012-01-19 6:16 ` [PATCH 03/10] MXS-MMC : change the DMA header file Huang Shijie
2012-01-19 6:16 ` [PATCH 04/10] MTD/GPMI " Huang Shijie
2012-01-19 6:16 ` [PATCH 05/10] ASoc " Huang Shijie
2012-01-19 6:16 ` [PATCH 06/10] MXS-DMA : add more flags for MXS-DMA Huang Shijie
2012-01-19 9:02 ` Russell King - ARM Linux
2012-01-19 9:31 ` Huang Shijie
2012-01-19 6:16 ` [PATCH 07/10] MXS-DMA : change the last parameter of mxs_dma_prep_slave_sg() Huang Shijie
2012-01-19 6:16 ` [PATCH 08/10] MXS-MMC : use the new DMA flags Huang Shijie
2012-01-19 6:16 ` [PATCH 09/10] MTD/GPMI : add a new field `gpmi_version` Huang Shijie
2012-01-19 6:16 ` [PATCH 10/10] MTD/GPMI : change the code for new DMA interface Huang Shijie
2012-01-19 9:10 ` Shawn Guo [this message]
2012-01-19 9:45 ` [PATCH 00/10] patch set about the MXS-DMA Wolfram Sang
2012-01-20 3:29 ` Huang Shijie
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=20120119091034.GH2247@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=LW@KARO-electronics.de \
--cc=alsa-devel@alsa-project.org \
--cc=artem.bityutskiy@intel.com \
--cc=b29396@freescale.com \
--cc=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.com \
--cc=vinod.koul@intel.com \
--cc=w.sang@pengutronix.de \
/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).