All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@linux.intel.com>
To: Boojin Kim <boojin.kim@samsung.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
	Russell King <linux@arm.linux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-samsung-soc@vger.kernel.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Dan Williams <dan.j.williams@intel.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 02/15] DMA: PL330: Update PL330 DMA API driver
Date: Mon, 29 Aug 2011 19:55:51 +0530	[thread overview]
Message-ID: <1314627951.1606.151.camel@vkoul-udesk3> (raw)
In-Reply-To: <1314627754.1606.145.camel@vkoul-udesk3>

On Mon, 2011-08-29 at 19:52 +0530, Vinod Koul wrote:
> On Mon, 2011-08-29 at 19:25 +0530, Vinod Koul wrote:
> > On Thu, 2011-08-25 at 11:13 +0900, Boojin Kim wrote:
> > > This patch updates following 3 items.
> > > @@ -69,6 +70,10 @@ struct dma_pl330_chan {
> > >  	 * NULL if the channel is available to be acquired.
> > >  	 */
> > >  	void *pl330_chid;
> > > +
> > > +	/* For D-to-M and M-to-D channels */
> > > +	int burst_sz; /* the peripheral fifo width */
> > > +	dma_addr_t fifo_addr;
> > >  };
> > Why should you store peripheral address and burst size in channel
> > structure. You should take these from the API and dma_slave_structure
> Ignore my comment for burst size, but is valid for peripheral address
Never mind this one as well, I need some more coffee...


-- 
~Vinod

WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@linux.intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 02/15] DMA: PL330: Update PL330 DMA API driver
Date: Mon, 29 Aug 2011 19:55:51 +0530	[thread overview]
Message-ID: <1314627951.1606.151.camel@vkoul-udesk3> (raw)
In-Reply-To: <1314627754.1606.145.camel@vkoul-udesk3>

On Mon, 2011-08-29 at 19:52 +0530, Vinod Koul wrote:
> On Mon, 2011-08-29 at 19:25 +0530, Vinod Koul wrote:
> > On Thu, 2011-08-25 at 11:13 +0900, Boojin Kim wrote:
> > > This patch updates following 3 items.
> > > @@ -69,6 +70,10 @@ struct dma_pl330_chan {
> > >  	 * NULL if the channel is available to be acquired.
> > >  	 */
> > >  	void *pl330_chid;
> > > +
> > > +	/* For D-to-M and M-to-D channels */
> > > +	int burst_sz; /* the peripheral fifo width */
> > > +	dma_addr_t fifo_addr;
> > >  };
> > Why should you store peripheral address and burst size in channel
> > structure. You should take these from the API and dma_slave_structure
> Ignore my comment for burst size, but is valid for peripheral address
Never mind this one as well, I need some more coffee...


-- 
~Vinod

  reply	other threads:[~2011-08-29 14:27 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  2:13 To use DMA generic APIs for Samsung DMA Boojin Kim
2011-08-25  2:13 ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 01/15] DMA: PL330: Add support runtime PM for PL330 DMAC Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 02/15] DMA: PL330: Update PL330 DMA API driver Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-26 14:48   ` Jassi Brar
2011-08-26 14:48     ` Jassi Brar
2011-08-29 13:55   ` Vinod Koul
2011-08-29 13:55     ` Vinod Koul
2011-08-29 14:22     ` Vinod Koul
2011-08-29 14:22       ` Vinod Koul
2011-08-29 14:25       ` Vinod Koul [this message]
2011-08-29 14:25         ` Vinod Koul
2011-08-25  2:13 ` [PATCH v7 03/15] DMA: PL330: Modify device_control() Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-26 15:19   ` Jassi Brar
2011-08-26 15:19     ` Jassi Brar
2011-08-25  2:13 ` [PATCH v7 04/15] DMA: PL330: Add DMA_CYCLIC capability Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-26 15:25   ` Jassi Brar
2011-08-26 15:25     ` Jassi Brar
2011-08-25  2:13 ` [PATCH v7 05/15] ARM: SAMSUNG: Update to use PL330-DMA driver Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 06/15] ARM: SAMSUNG: Add common DMA operations Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 07/15] ARM: EXYNOS4: Use generic DMA PL330 driver Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 08/15] ARM: S5PV210: " Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 09/15] ARM: S5PC100: " Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 10/15] ARM: S5P64X0: " Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 11/15] ARM: SAMSUNG: Remove S3C-PL330-DMA driver Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 12/15] spi/s3c64xx: Add support DMA engine API Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 13/15] spi/s3c64xx: Merge dma control code Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 14/15] ASoC: Samsung: Update DMA interface Boojin Kim
2011-08-25  2:13   ` Boojin Kim
2011-08-25  2:13 ` [PATCH v7 15/15] ARM: SAMSUNG: Remove Samsung specific enum type for dma direction Boojin Kim
2011-08-25  2:13   ` Boojin Kim

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=1314627951.1606.151.camel@vkoul-udesk3 \
    --to=vinod.koul@linux.intel.com \
    --cc=boojin.kim@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dan.j.williams@intel.com \
    --cc=grant.likely@secretlab.ca \
    --cc=jassisinghbrar@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.