From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Frank Li <Frank.li@nxp.com>
Cc: vkoul@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
peng.fan@nxp.com, joy.zou@nxp.com, shenwei.wang@nxp.com,
imx@lists.linux.dev
Subject: Re: [PATCH v9 00/13] dmaengine: edma: add freescale edma v3 support
Date: Mon, 3 Jul 2023 17:00:50 +0200 [thread overview]
Message-ID: <cf2978dc-9ef9-0b3c-911a-7da97977e412@linaro.org> (raw)
In-Reply-To: <ZKLfB7putFfLlAoH@lizhi-Precision-Tower-5810>
On 03/07/2023 16:45, Frank Li wrote:
> On Sun, Jul 02, 2023 at 10:22:22PM +0200, Krzysztof Kozlowski wrote:
>> On 28/06/2023 16:45, Frank Li wrote:
>>> On Tue, Jun 20, 2023 at 04:12:08PM -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.
>>>>
>>>> Patch 1-11:
>>>> These patches primarily focus on cleaning up and refactoring the existing
>>>> fsl_edma driver code. This is to accommodate the upcoming changes and new
>>>> features introduced with the eDMA v3.
>>>>
>>>> Patch 12:
>>>> This patch introduces support for eDMA v3. In addition, this patch has
>>>> been designed with an eye towards future upgradability, specifically for
>>>> transitioning to eDMA v5. The latter involves a significant upgrade
>>>> where the TCD address would need to support 64 bits.
>>>>
>>>> Patch 13:
>>>> This patch focuses on the device tree bindings and their modifications
>>>> to properly handle and integrate the changes brought about by eDMA v3
>>>
>>> @vkoul:
>>> Do you have chance to check these patches? Any chance to come into 6.5
>>> All audio parts of i.MX8x and i.MX9 was dependent on these patches.
>>
>> Why do you ping during the merge window?
>>
>> v6.5? And what about having it in next for two weeks? One thing is to
>> ping for something forgotten, different thing is to try squeeze patches
>> skipping our process.
>
> I saw dmaengine tree have not update over 5 weeks.
> https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git/
Then you should have pinged during that time.
> And vkoul have not sent out pull request yet. So I just want to check
> if possible.
It is merge window. Patches are supposed to be in next for two weeks
before merge window.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-07-03 15:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 20:12 Frank Li
2023-06-20 20:12 ` [PATCH v9 01/13] dmaengine: fsl-edma: fix build error when arch is s390 Frank Li
2023-07-07 5:37 ` Vinod Koul
2023-06-20 20:12 ` [PATCH v9 02/13] dmaengine: fsl-edma: clean up EXPORT_SYMBOL_GPL in fsl-edma-common.c Frank Li
2023-07-07 5:39 ` Vinod Koul
2023-06-20 20:12 ` [PATCH v9 03/13] dmaengine: fsl-edma: clean up fsl_edma_irq_exit() Frank Li
2023-07-07 5:41 ` Vinod Koul
2023-06-20 20:12 ` [PATCH v9 04/13] dmaengine: fsl-edma: transition from bool fields to bitmask flags in drvdata Frank Li
2023-06-20 20:12 ` [PATCH v9 05/13] dmaengine: fsl-edma: Remove enum edma_version Frank Li
2023-06-20 20:12 ` [PATCH v9 06/13] dmaengine: fsl-edma: move common IRQ handler to common.c Frank Li
2023-06-20 20:12 ` [PATCH v9 07/13] dmaengine: fsl-edma: simply ATTR_DSIZE and ATTR_SSIZE by using ffs() Frank Li
2023-06-20 20:12 ` [PATCH v9 08/13] dmaengine: fsl-edma: refactor using devm_clk_get_enabled Frank Li
2023-06-20 20:12 ` [PATCH v9 09/13] dmaengine: fsl-edma: move clearing of register interrupt into setup_irq function Frank Li
2023-06-20 20:12 ` [PATCH v9 10/13] dmaengine: fsl-edma: refactor chan_name setup and safety Frank Li
2023-06-20 20:12 ` [PATCH v9 11/13] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan Frank Li
2023-06-20 20:12 ` [PATCH v9 12/13] dmaengine: fsl-edma: integrate v3 support Frank Li
2023-07-07 5:44 ` Vinod Koul
2023-07-07 16:21 ` Frank Li
2023-07-09 10:46 ` Vinod Koul
2023-06-20 20:12 ` [PATCH v9 13/13] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string Frank Li
2023-07-07 5:45 ` Vinod Koul
2023-06-28 14:45 ` [PATCH v9 00/13] dmaengine: edma: add freescale edma v3 support Frank Li
2023-07-02 20:22 ` Krzysztof Kozlowski
2023-07-03 14:45 ` Frank Li
2023-07-03 15:00 ` Krzysztof Kozlowski [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=cf2978dc-9ef9-0b3c-911a-7da97977e412@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=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
all inboxes | Powered by JetHome®