dmaengine Archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	"open list:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM"
	<dmaengine@vger.kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dmaengine: mxs-dma: switch from dma_coherent to dma_pool
Date: Thu, 22 Feb 2024 19:17:03 +0530	[thread overview]
Message-ID: <ZddQVzs-VvjraJAf@matsya> (raw)
In-Reply-To: <ZdTjrzYIiD8pwHk8@lizhi-Precision-Tower-5810>

On 20-02-24, 12:38, Frank Li wrote:
> On Mon, Feb 19, 2024 at 01:23:22PM -0300, Fabio Estevam wrote:
> > On Mon, Feb 19, 2024 at 12:57 PM Frank Li <Frank.Li@nxp.com> wrote:
> > >
> > > From: Han Xu <han.xu@nxp.com>
> > >
> > > Using dma_pool to manage dma descriptor memory.
> > 
> > Please clearly describe the motivation for doing this.
> 
> This try to fix a cma_alloc failure. But it is not correct to use dma_pool.
> let's work out a better method.

Good one, but this should be in log :-)

> 
> Frank

-- 
~Vinod

      reply	other threads:[~2024-02-22 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 15:57 [PATCH 1/1] dmaengine: mxs-dma: switch from dma_coherent to dma_pool Frank Li
2024-02-19 16:23 ` Fabio Estevam
2024-02-20 17:38   ` Frank Li
2024-02-22 13:47     ` Vinod Koul [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=ZddQVzs-VvjraJAf@matsya \
    --to=vkoul@kernel.org \
    --cc=Frank.li@nxp.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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 read-only IMAP folder(s) and NNTP newsgroup(s).