From: Frank Li <Frank.Li@nxp.com>
To: 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,
vkoul@kernel.org
Subject: [PATCH 0/4] dmaengine: fsl-edma: integrate TCD64 support for 64bit physical address
Date: Thu, 9 Nov 2023 16:20:55 -0500 [thread overview]
Message-ID: <20231109212059.1894646-1-Frank.Li@nxp.com> (raw)
first 2 patch is prepare, No function change.
3rd patch is dt-bind doc
4rd patch is actuall support TCD64
Frank Li (4):
dmaengine: fsl-edma: involve help macro fsl_edma_set(get)_tcd()
dmaengine: fsl-edma: add address for channel mux register in
fsl_edma_chan
dt-bindings: fsl-dma: fsl-edma: add fsl,imx95-edma5 compatible string
dmaengine: fsl-edma: integrate TCD64 support for i.MX95
.../devicetree/bindings/dma/fsl,edma.yaml | 2 +
drivers/dma/fsl-edma-common.c | 85 ++++++------
drivers/dma/fsl-edma-common.h | 126 ++++++++++++++++--
drivers/dma/fsl-edma-main.c | 17 +++
4 files changed, 178 insertions(+), 52 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-09 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 21:20 Frank Li [this message]
2023-11-09 21:20 ` [PATCH 1/4] dmaengine: fsl-edma: involve help macro fsl_edma_set(get)_tcd() Frank Li
2023-11-09 21:20 ` [PATCH 2/4] dmaengine: fsl-edma: add address for channel mux register in fsl_edma_chan Frank Li
2023-11-09 21:20 ` [PATCH 3/4] dt-bindings: fsl-dma: fsl-edma: add fsl,imx95-edma5 compatible string Frank Li
2023-11-10 7:56 ` Krzysztof Kozlowski
2023-11-09 21:20 ` [PATCH 4/4] dmaengine: fsl-edma: integrate TCD64 support for i.MX95 Frank Li
2023-11-10 6:09 ` kernel test robot
2023-11-10 9:16 ` kernel test robot
2023-11-10 14:28 ` kernel test robot
2023-11-10 14:50 ` Krzysztof Kozlowski
2023-11-10 14:59 ` Frank Li
2023-11-10 15:10 ` Krzysztof Kozlowski
2023-11-10 15:36 ` Frank Li
2023-11-10 15:52 ` Krzysztof Kozlowski
2023-11-10 16:08 ` Frank Li
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=20231109212059.1894646-1-Frank.Li@nxp.com \
--to=frank.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--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 \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).