From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 04/14] DMA: PL330: Add DMA_CYCLIC capability
Date: Mon, 25 Jul 2011 11:36:29 +0100 [thread overview]
Message-ID: <20110725103629.GF9653@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <002001cc4ab6$0d7cd590$287680b0$%kim@samsung.com>
On Mon, Jul 25, 2011 at 07:31:45PM +0900, Boojin Kim wrote:
> > On Mon, Jul 25, 2011 at 10:28:22AM +0900, Boojin Kim wrote:
> > > +static void pl330_tasklet_cyclic(unsigned long data)
> > > +{
> > > + struct dma_pl330_chan *pch = (struct dma_pl330_chan *)data;
> > > + struct dma_pl330_desc *desc, *_dt;
> > > + unsigned long flags;
> > > + LIST_HEAD(list);
> > > +
> > > + spin_lock_irqsave(&pch->lock, flags);
> > ...
> > > + callback = desc->txd.callback;
> > > + if (callback)
> > > + callback(desc->txd.callback_param);
> >
> > On this again - what if the callback wants to terminate the DMA activity
> > because there's no more audio data to be sent/received from the device?
>
> Do you mean what is happened if the callback() is called after channel is
> terminated ?
> Or What is happened if Callback() calls 'dma_release_channel()' to terminate
> DMA?
No. I mean what if the callback wants to call dmaengine_terminate_all().
> > > + if (!pch->cyclic_task) {
> > > + pch->cyclic_task =
> > > + kmalloc(sizeof(struct tasklet_struct), GFP_KERNEL);
> > > + tasklet_init(pch->cyclic_task,
> > > + pl330_tasklet_cyclic, (unsigned int)pch);
> >
> > Here you allocate memory for the cyclic task. Above you set this pointer
> > to NULL. That sounds like a memory leak to me. Why are you kmallocing
> > this memory - why can't it be part of the dma_pl330_chan structure? It's
> > only 28 bytes.
>
> It's my mistake. I should have been free of the memory.
>
> And the reason why I use kmalloc for 'cyclic_task' is following.
> This memory size for 'cyclic_tasklet' is the 896 bytes ( = the number of
> channel * sizeof(struct tasklet_struct)= 32*28) for each DMAC. And This
> memory size is increased according to the number of DMAC.
> And Samsung has the DMAC that is dedicated for Mem-to-Mem operation. If I
> make 'cyclic_task' be part of dma_pl330_chan, this DMAC that is dedicated
> for Mem-to-Mem operation should hold unused data.
> So, I think it's loss that all dma channels hold own 'cyclic_task'.
Could you re-use the tasklet that already exists?
next prev parent reply other threads:[~2011-07-25 10:36 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 1:28 [RESEND] [PATCH V4 0/14] To use DMA generic APIs for Samsung DMA Boojin Kim
2011-07-25 1:28 ` [PATCH V4 01/14] DMA: PL330: Add support runtime PM for PL330 DMAC Boojin Kim
2011-07-26 6:03 ` Chanwoo Choi
2011-07-25 1:28 ` [PATCH V4 02/14] DMA: PL330: Update PL330 DMA API driver Boojin Kim
2011-07-25 8:57 ` Jassi Brar
2011-07-25 9:48 ` Boojin Kim
2011-07-25 1:28 ` [PATCH V4 03/14] DMA: PL330: Support DMA_SLAVE_CONFIG command Boojin Kim
2011-07-25 10:26 ` Vinod Koul
2011-07-25 12:51 ` Boojin Kim
2011-07-25 13:48 ` Vinod Koul
2011-07-26 13:04 ` Boojin Kim
2011-07-26 13:12 ` Russell King - ARM Linux
2011-07-25 1:28 ` [PATCH V4 04/14] DMA: PL330: Add DMA_CYCLIC capability Boojin Kim
2011-07-25 9:27 ` Russell King - ARM Linux
2011-07-25 10:31 ` Boojin Kim
2011-07-25 10:36 ` Russell King - ARM Linux [this message]
2011-07-25 10:48 ` Vinod Koul
2011-07-25 10:57 ` Russell King - ARM Linux
2011-07-25 11:01 ` Vinod Koul
2011-07-25 11:39 ` Russell King - ARM Linux
2011-07-25 12:01 ` Vinod Koul
2011-07-26 7:57 ` [PATCH] Improve slave/cyclic DMA engine documentation (was: [PATCH V4 04/14] DMA: PL330: Add DMA_CYCLIC capability) Russell King - ARM Linux
2011-07-26 9:35 ` Vinod Koul
2011-07-26 14:37 ` Jassi Brar
2011-07-26 17:20 ` Russell King - ARM Linux
2011-07-26 17:55 ` Jassi Brar
2011-07-26 18:03 ` Grant Likely
2011-07-26 18:16 ` Russell King - ARM Linux
2011-07-27 2:38 ` Vinod Koul
2011-07-27 9:01 ` Russell King - ARM Linux
2011-07-27 9:06 ` Koul, Vinod
2011-07-26 13:25 ` Russell King - ARM Linux
2011-07-25 12:36 ` [PATCH V4 04/14] DMA: PL330: Add DMA_CYCLIC capability Boojin Kim
2011-07-25 12:34 ` Boojin Kim
2011-07-25 11:24 ` Jassi Brar
2011-07-26 12:28 ` Boojin Kim
2011-07-25 1:28 ` [PATCH V4 05/14] ARM: SAMSUNG: Update to use PL330-DMA driver Boojin Kim
2011-07-25 10:52 ` Vinod Koul
2011-07-25 11:31 ` Jassi Brar
2011-07-25 1:28 ` [PATCH V4 06/14] ARM: SAMSUNG: Add common DMA operations Boojin Kim
2011-07-25 9:36 ` Russell King - ARM Linux
2011-07-25 9:57 ` Boojin Kim
2011-07-25 11:51 ` Jassi Brar
2011-07-26 8:02 ` Russell King - ARM Linux
2011-07-26 17:43 ` Jassi Brar
2011-07-26 18:14 ` Russell King - ARM Linux
2011-07-26 19:54 ` Jassi Brar
2011-07-26 9:35 ` Boojin Kim
2011-07-27 1:33 ` Jassi Brar
2011-07-27 5:17 ` Boojin Kim
2011-07-27 7:57 ` Jassi Brar
2011-07-28 0:38 ` Boojin Kim
2011-07-25 1:28 ` [PATCH V4 07/14] ARM: EXYNOS4: Use generic DMA PL330 driver Boojin Kim
2011-07-25 11:59 ` Jassi Brar
2011-07-25 12:59 ` Boojin Kim
2011-07-25 1:28 ` [PATCH V4 08/14] ARM: S5PV210: " Boojin Kim
2011-07-25 1:28 ` [PATCH V4 09/14] ARM: S5PC100: " Boojin Kim
2011-07-25 1:28 ` [PATCH V4 10/14] ARM: S5P64X0: " Boojin Kim
2011-07-25 1:28 ` [PATCH V4 11/14] ARM: SAMSUNG: Remove S3C-PL330-DMA driver Boojin Kim
2011-07-25 1:28 ` [PATCH V4 12/14] spi/s3c64xx: Add support DMA engine API Boojin Kim
2011-07-25 9:40 ` Russell King - ARM Linux
2011-07-25 10:34 ` Boojin Kim
2011-07-25 11:17 ` Vinod Koul
2011-07-26 9:31 ` Boojin Kim
2011-07-26 10:14 ` Vinod Koul
2011-07-27 5:05 ` Boojin Kim
2011-07-25 1:28 ` [PATCH V4 13/14] ASoC: Samsung: Update DMA interface Boojin Kim
2011-07-25 1:28 ` [PATCH V4 14/14] ARM: SAMSUNG: Remove Samsung specific enum type for dma direction Boojin Kim
2011-07-25 12:08 ` Jassi Brar
2011-07-25 21:15 ` Grant Likely
2011-07-28 1:23 ` Boojin Kim
2011-07-25 10:17 ` [RESEND] [PATCH V4 0/14] To use DMA generic APIs for Samsung DMA Vinod Koul
2011-07-25 11:09 ` Vinod Koul
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=20110725103629.GF9653@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).