From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] dma: Add Freescale eDMA engine driver support
Date: Mon, 5 Aug 2013 21:15:51 +0530 [thread overview]
Message-ID: <20130805154551.GP29095@intel.com> (raw)
In-Reply-To: <20991.23049.78707.457046@ipc1.ka-ro>
On Mon, Aug 05, 2013 at 09:53:45AM +0200, Lothar Wa?mann wrote:
> Hi,
>
> Jingchang Lu writes:
> > Add Freescale enhanced direct memory(eDMA) controller support.
> > The eDMA controller deploys DMAMUXs routing DMA request sources(slot)
> > to eDMA channels.
> > This module can be found on Vybrid and LS-1 SoCs.
> >
> [...]
> > +static struct fsl_edma_desc *fsl_edma_alloc_desc(struct fsl_edma_chan *fsl_chan,
> > + int sg_len)
> > +{
> > + struct fsl_edma_desc *fsl_desc;
> > + int size, i;
> > +
> > + size = sizeof(struct fsl_edma_desc);
> > + size += sizeof(struct fsl_edma_sw_tcd) * sg_len;
> > + fsl_desc = kzalloc(size, GFP_KERNEL);
> > + if (!fsl_desc)
> > + return NULL;
> > +
> > + fsl_desc->echan = fsl_chan;
> > + fsl_desc->n_tcds = sg_len;
> > + for (i = 0; i < sg_len; i++) {
> > + fsl_desc->tcd[i].vtcd = dma_pool_alloc(fsl_chan->tcd_pool,
> > + GFP_ATOMIC, &fsl_desc->tcd[i].ptcd);
> >
> Why is this called with GFP_ATOMIC while fsl_desc above is being
> allocated with GFP_KERNEL?
Both need to be GFP_ATOMIC, better they need to be GFP_NOWAIT.
~Vinod
next prev parent reply other threads:[~2013-08-05 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 6:07 [PATCH v2 2/3] ARM: dts: vf610: Add eDMA node Jingchang Lu
2013-08-05 6:07 ` [PATCH v2 3/3] dma: Add Freescale eDMA engine driver support Jingchang Lu
2013-08-05 7:53 ` Lothar Waßmann
2013-08-05 9:44 ` Lu Jingchang-B35083
2013-08-05 15:45 ` Vinod Koul [this message]
2013-08-05 16:34 ` Vinod Koul
2013-08-06 1:24 ` Lu Jingchang-B35083
2013-08-06 4:25 ` Vinod Koul
2013-08-06 5:15 ` Lu Jingchang-B35083
2013-08-05 10:32 ` [PATCH v2 2/3] ARM: dts: vf610: Add eDMA node Sascha Hauer
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=20130805154551.GP29095@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).