From: Frank Li <Frank.li@nxp.com>
To: joy.zou@nxp.com, vkoul@kernel.org
Cc: devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
imx@lists.linux.dev, 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 v4 0/6] dmaengine: fsl-edma: integrate TCD64 support for 64bit physical address
Date: Mon, 22 Jan 2024 11:55:26 -0500 [thread overview]
Message-ID: <Za6d/lSARdxpqU4e@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20231221153528.1588049-1-Frank.Li@nxp.com>
On Thu, Dec 21, 2023 at 10:35:22AM -0500, Frank Li wrote:
> Change from v3 to v4.
> Fixed tcd64 type as fsl_edma_hw_tcd64
>
> Change from v2 to v3:
> - fix sparse build warning
>
> Change from v1 to v2:
> - fixed mcf-edma-main.c build error.
> - fixed readq build error. readq actually is not atomic read in imx95.
> So split to two ioread32\iowrite32.
> It needs read at least twice to avoid lower 32 bit part wrap during read
> up 32bit part.
>
> first 2 patch is prepare, No function change.
> 3rd patch is dt-bind doc
> 4rd patch is actuall support TCD64
@vnod:
Could you please check these patches? I still have more patches,
which depended on this.
eDMA is used for cross whole i.MX chips.
Frank
>
> Frank Li (6):
> dmaengine: fsl-edma: involve help macro fsl_edma_set(get)_tcd()
> dmaengine: fsl-edma: fix spare build warning
> dmaengine: fsl-edma: add address for channel mux register in
> fsl_edma_chan
> dmaengine: mcf-edma: utilize edma_write_tcdreg() macro for TCD Access
> 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 | 101 ++++++-----
> drivers/dma/fsl-edma-common.h | 161 ++++++++++++++++--
> drivers/dma/fsl-edma-main.c | 19 ++-
> drivers/dma/mcf-edma-main.c | 2 +-
> 5 files changed, 223 insertions(+), 62 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-01-22 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:35 [PATCH v4 0/6] dmaengine: fsl-edma: integrate TCD64 support for 64bit physical address Frank Li
2023-12-21 15:35 ` [PATCH v4 1/6] dmaengine: fsl-edma: involve help macro fsl_edma_set(get)_tcd() Frank Li
2023-12-21 15:35 ` [PATCH v4 2/6] dmaengine: fsl-edma: fix spare build warning Frank Li
2023-12-21 15:35 ` [PATCH v4 3/6] dmaengine: fsl-edma: add address for channel mux register in fsl_edma_chan Frank Li
2023-12-21 15:35 ` [PATCH v4 4/6] dmaengine: mcf-edma: utilize edma_write_tcdreg() macro for TCD Access Frank Li
2023-12-21 15:35 ` [PATCH v4 5/6] dt-bindings: fsl-dma: fsl-edma: add fsl,imx95-edma5 compatible string Frank Li
2023-12-21 15:35 ` [PATCH v4 6/6] dmaengine: fsl-edma: integrate TCD64 support for i.MX95 Frank Li
2024-01-22 16:55 ` Frank Li [this message]
2024-01-31 15:33 ` [PATCH v4 0/6] dmaengine: fsl-edma: integrate TCD64 support for 64bit physical address Frank Li
2024-02-07 8:49 ` Vinod Koul
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=Za6d/lSARdxpqU4e@lizhi-Precision-Tower-5810 \
--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).