From: Manivannan Sadhasivam <mani@kernel.org>
To: "Köry Maincent" <kory.maincent@bootlin.com>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
Serge Semin <fancer.lancer@gmail.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Vinod Koul <vkoul@kernel.org>,
Cai Huoqing <cai.huoqing@linux.dev>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Herve Codina <herve.codina@bootlin.com>
Subject: Re: [PATCH v6 0/6] Fix support of dw-edma HDMA NATIVE IP in remote setup
Date: Sat, 20 Jan 2024 20:43:40 +0530 [thread overview]
Message-ID: <20240120151340.GA6371@thinkpad> (raw)
In-Reply-To: <20240112111637.01a5ea21@kmaincent-XPS-13-7390>
On Fri, Jan 12, 2024 at 11:16:37AM +0100, Köry Maincent wrote:
> On Wed, 22 Nov 2023 22:42:42 +0530
> Manivannan Sadhasivam <mani@kernel.org> wrote:
>
> > > For all of that you'll need to fix the
> > > dw_pcie_edma_find_chip()/dw_pcie_edma_detect() method somehow.
> > >
> > > Alternatively, to keep things simple you can convert the
> > > dw_pcie_edma_find_chip()/dw_pcie_edma_detect() methods to just relying
> > > on the HDMA settings being fully specified by the low-level drivers.
> > >
> >
> > This looks like the best possible solution at the moment. Thanks for the
> > insight!
> >
> > I will post the patches together with the HDMA enablement ones.
>
> Hello Manivannan,
>
> What is the status of this series?
> Do you want to wait for designware-ep.c to be HDMA compatible before merging
> the fixes? Do you expect us to do something? We can't work on the
> designware-ep.c driver as we do not have such hardware.
> Shouldn't fixes be merged as soon as possible?
>
I've reviewed all the patches, but I do not merge them. It is upto the dmaengine
maintainer (Vinod) to merge the patches. Anyway, we are in v6.8 merge window, so
you can rebase on top of v6.8-rc1 once released and post the patches.
- Mani
> Regards,
> --
> Köry Maincent, Bootlin
> Embedded Linux and kernel engineering
> https://bootlin.com
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-01-20 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 10:03 [PATCH v6 0/6] Fix support of dw-edma HDMA NATIVE IP in remote setup Kory Maincent
2023-11-17 10:03 ` [PATCH v6 1/6] dmaengine: dw-edma: Fix the ch_count hdma callback Kory Maincent
2023-11-17 10:03 ` [PATCH v6 2/6] dmaengine: dw-edma: Fix wrong interrupt bit set for HDMA Kory Maincent
2023-11-17 10:03 ` [PATCH v6 3/6] dmaengine: dw-edma: HDMA_V0_REMOTEL_STOP_INT_EN typo fix Kory Maincent
2023-11-17 10:03 ` [PATCH v6 4/6] dmaengine: dw-edma: Add HDMA remote interrupt configuration Kory Maincent
2023-11-17 10:03 ` [PATCH v6 5/6] dmaengine: dw-edma: HDMA: Add sync read before starting the DMA transfer in remote setup Kory Maincent
2023-11-17 10:03 ` [PATCH v6 6/6] dmaengine: dw-edma: eDMA: " Kory Maincent
2023-11-21 6:26 ` [PATCH v6 0/6] Fix support of dw-edma HDMA NATIVE IP " Manivannan Sadhasivam
2023-11-21 10:55 ` Serge Semin
2023-11-21 12:08 ` Manivannan Sadhasivam
2023-11-21 15:36 ` Serge Semin
2023-11-22 17:12 ` Manivannan Sadhasivam
2024-01-12 10:16 ` Köry Maincent
2024-01-20 15:13 ` Manivannan Sadhasivam [this message]
2024-01-22 10:38 ` Köry Maincent
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=20240120151340.GA6371@thinkpad \
--to=mani@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=dmaengine@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=herve.codina@bootlin.com \
--cc=kory.maincent@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.