From: Vinod Koul <vinod.koul@intel.com>
To: Alexander Popov <a13xp0p0v88@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Arnd Bergmann <arnd@arndb.de>, Gerhard Sittig <gsi@denx.de>,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>,
dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Anatolij Gustschin <agust@denx.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH RFC v12 3/7] dma: mpc512x: add support for peripheral transfers
Date: Wed, 21 May 2014 08:44:20 +0530 [thread overview]
Message-ID: <20140521031420.GE21128@intel.com> (raw)
In-Reply-To: <CAF0T0X6XBe-xcgXJ3M0QhxeHuK7H+H_neAWn_ChFxU6pr-QqXQ@mail.gmail.com>
On Thu, May 08, 2014 at 01:49:20PM +0400, Alexander Popov wrote:
> >> + case DMA_SLAVE_CONFIG:
> >> + /*
> >> + * Constraints:
> >> + * - only transfers between a peripheral device and
> >> + * memory are supported;
> >> + * - minimal transfer chunk is 4 bytes and consequently
> >> + * source and destination addresses must be 4-byte aligned
> >> + * and transfer size must be aligned on (4 * maxburst)
> >> + * boundary;
> >> + * - during the transfer RAM address is being incremented by
> >> + * the size of minimal transfer chunk;
> >> + * - peripheral port's address is constant during the transfer.
> >> + */
> >> +
> >> + cfg = (void *)arg;
> >> +
> >> + if (cfg->src_addr_width != DMA_SLAVE_BUSWIDTH_4_BYTES ||
> >> + cfg->dst_addr_width != DMA_SLAVE_BUSWIDTH_4_BYTES ||
> > and why this limtation, doesnt seem covered above?
> I created this limitation because FIFO registers of LPC and SDHC
> support _only_ 4-byte access.
>
> I tried to cover this limitation in the statement "minimal transfer chunk
> is 4 bytes". Should I make it more explicit?
expose these as capablities and try to use these in your client driver. Already
we have audio drivers using those...
--
~Vinod
next prev parent reply other threads:[~2014-05-21 3:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 13:53 [PATCH RFC v12 0/7] MPC512x DMA slave s/g support, OF DMA lookup Alexander Popov
2014-04-23 13:53 ` Alexander Popov
2014-04-23 13:53 ` [PATCH RFC v12 1/7] dma: mpc512x: reorder mpc8308 specific instructions Alexander Popov
2014-05-02 17:06 ` Vinod Koul
2014-04-23 13:53 ` [PATCH RFC v12 2/7] dma: mpc512x: separate 'compatible' values for MPC512x and MPC8308 Alexander Popov
2014-04-23 13:53 ` Alexander Popov
2014-05-02 17:07 ` Vinod Koul
2014-05-02 17:07 ` Vinod Koul
2014-04-23 13:53 ` [PATCH RFC v12 3/7] dma: mpc512x: add support for peripheral transfers Alexander Popov
2014-05-02 17:03 ` Vinod Koul
2014-05-08 9:49 ` Alexander Popov
2014-05-21 3:14 ` Vinod Koul [this message]
2014-04-23 13:53 ` [PATCH RFC v12 4/7] dma: mpc512x: fix freeing resources in mpc_dma_probe() and mpc_dma_remove() Alexander Popov
2014-05-02 17:07 ` Vinod Koul
2014-04-23 13:53 ` [PATCH RFC v12 5/7] dma: of: add common xlate function for matching by channel id Alexander Popov
2014-04-23 13:53 ` Alexander Popov
2014-05-02 17:04 ` Vinod Koul
2014-05-02 17:04 ` Vinod Koul
2014-04-23 13:53 ` [PATCH RFC v12 6/7] dma: mpc512x: add device tree binding document Alexander Popov
2014-04-23 13:53 ` Alexander Popov
2014-04-23 13:53 ` [PATCH RFC v12 7/7] dma: mpc512x: register for device tree channel lookup Alexander Popov
2014-04-23 13:53 ` Alexander Popov
2014-04-30 5:46 ` [PATCH RFC v12 0/7] MPC512x DMA slave s/g support, OF DMA lookup Alexander Popov
2014-04-30 5:46 ` Alexander Popov
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=20140521031420.GE21128@intel.com \
--to=vinod.koul@intel.com \
--cc=a13xp0p0v88@gmail.com \
--cc=agust@denx.de \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gsi@denx.de \
--cc=lars@metafoo.de \
--cc=linuxppc-dev@lists.ozlabs.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.