From: Vinod Koul <vkoul@kernel.org>
To: frank.li@nxp.com, Frank Li <Frank.Li@nxp.com>
Cc: devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
imx@lists.linux.dev, joy.zou@nxp.com,
krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
peng.fan@nxp.com, robh+dt@kernel.org, shenwei.wang@nxp.com
Subject: Re: [PATCH v10 00/12] dmaengine: edma: add freescale edma v3 support
Date: Tue, 22 Aug 2023 20:12:28 +0530 [thread overview]
Message-ID: <169271534836.283614.7735690823757895003.b4-ty@kernel.org> (raw)
In-Reply-To: <20230707190029.476005-1-Frank.Li@nxp.com>
On Fri, 07 Jul 2023 15:00:17 -0400, Frank Li wrote:
> This patch series introduces support for the eDMA version 3 from
> Freescale. The eDMA v3 brings alterations in the register layout,
> particularly, the separation of channel control registers into
> different channels. The Transfer Control Descriptor (TCD) layout,
> however, remains identical with only the offset being changed.
>
> The first 11 patches aim at tidying up the existing Freescale
> eDMA code and laying the groundwork for the integration of eDMA v3
> support.
>
> [...]
Applied, thanks!
[01/12] dmaengine: fsl-edma: fix build error when arch is s390
commit: 8b9aee8073a5f3e0c2e418d45a7969270ea576c6
[02/12] dmaengine: fsl-edma: clean up EXPORT_SYMBOL_GPL in fsl-edma-common.c
commit: 66aac8ea0a6c79729f99087b1c5a596938e5d838
[03/12] dmaengine: fsl-edma: transition from bool fields to bitmask flags in drvdata
commit: 9e006b243962a42f6927d2d9fe1a7b0a29f45265
[04/12] dmaengine: fsl-edma: Remove enum edma_version
commit: c26e611433aaa064691343c0168f4671eb5cfa42
[05/12] dmaengine: fsl-edma: move common IRQ handler to common.c
commit: 79434f9b97361601e65e0f5576e9760fefebf19a
[06/12] dmaengine: fsl-edma: simply ATTR_DSIZE and ATTR_SSIZE by using ffs()
commit: ee2dda06465a3b0f533c829a5bdc2ff15588d8e0
[07/12] dmaengine: fsl-edma: refactor using devm_clk_get_enabled
commit: a9903de3aa16731846bf924342eca44bdabe9be6
[08/12] dmaengine: fsl-edma: move clearing of register interrupt into setup_irq function
commit: f5b3ba52f36adcda7801fba99c414975f19c85d4
[09/12] dmaengine: fsl-edma: refactor chan_name setup and safety
commit: 9b05554c5ca6829a60c610191d45f244d8726e95
[10/12] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan
commit: 7536f8b371adcc1c4f7ed7ca579da24bdeb14b6f
[11/12] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string
commit: 6eb439dff645a1f61a710abfc0d37a50e4d43d1a
[12/12] dmaengine: fsl-edma: integrate v3 support
commit: 72f5801a4e2b7122ed8ff5672ea965a0b3458e6b
Best regards,
--
~Vinod
prev parent reply other threads:[~2023-08-22 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 19:00 Frank Li
2023-07-07 19:00 ` [PATCH v10 01/12] dmaengine: fsl-edma: fix build error when arch is s390 Frank Li
2023-07-07 19:00 ` [PATCH v10 02/12] dmaengine: fsl-edma: clean up EXPORT_SYMBOL_GPL in fsl-edma-common.c Frank Li
2023-07-07 19:00 ` [PATCH v10 03/12] dmaengine: fsl-edma: transition from bool fields to bitmask flags in drvdata Frank Li
2023-07-07 19:00 ` [PATCH v10 04/12] dmaengine: fsl-edma: Remove enum edma_version Frank Li
2023-07-07 19:00 ` [PATCH v10 05/12] dmaengine: fsl-edma: move common IRQ handler to common.c Frank Li
2023-07-07 19:00 ` [PATCH v10 06/12] dmaengine: fsl-edma: simply ATTR_DSIZE and ATTR_SSIZE by using ffs() Frank Li
2023-07-07 19:00 ` [PATCH v10 07/12] dmaengine: fsl-edma: refactor using devm_clk_get_enabled Frank Li
2023-07-07 19:00 ` [PATCH v10 08/12] dmaengine: fsl-edma: move clearing of register interrupt into setup_irq function Frank Li
2023-07-07 19:00 ` [PATCH v10 09/12] dmaengine: fsl-edma: refactor chan_name setup and safety Frank Li
2023-07-07 19:00 ` [PATCH v10 10/12] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan Frank Li
2023-07-07 19:00 ` [PATCH v10 11/12] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string Frank Li
2023-07-07 19:00 ` [PATCH v10 12/12] dmaengine: fsl-edma: integrate v3 support Frank Li
2023-07-19 18:01 ` [PATCH v10 00/12] dmaengine: edma: add freescale edma " Frank Li
2023-07-31 14:49 ` Frank Li
2023-08-22 14:42 ` Vinod Koul [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=169271534836.283614.7735690823757895003.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=joy.zou@nxp.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shenwei.wang@nxp.com \
/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®