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/ And vkoul have not sent out pull request yet. So I just want to check if possible. Frank > > Best regards, > Krzysztof >
