From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v8 2/2] dmaengine: add Qualcomm BAM dma driver
Date: Sun, 02 Mar 2014 22:49:12 -0800 [thread overview]
Message-ID: <1393829352.13719.73.camel@joe-AO722> (raw)
In-Reply-To: <1393828245-18766-3-git-send-email-agross@codeaurora.org>
On Mon, 2014-03-03 at 00:30 -0600, Andy Gross wrote:
> Add the DMA engine driver for the QCOM Bus Access Manager (BAM) DMA controller
> found in the MSM 8x74 platforms.
>
> Each BAM DMA device is associated with a specific on-chip peripheral. Each
> channel provides a uni-directional data transfer engine that is capable of
> transferring data between the peripheral and system memory (System mode), or
> between two peripherals (BAM2BAM).
[]
trivia:
> +static u32 process_channel_irqs(struct bam_device *bdev)
> +{
[]
> + for (i = 0; i < bdev->num_channels; i++) {
> + struct bam_chan *bchan = &bdev->channels[i];
> + if (srcs & BIT(i)) {
> + /* clear pipe irq */
> + pipe_stts = readl_relaxed(bdev->regs +
> + BAM_P_IRQ_STTS(i));
> +
> + writel_relaxed(pipe_stts, bdev->regs +
> + BAM_P_IRQ_CLR(i));
> +
> + spin_lock_irqsave(&bchan->vc.lock, flags);
> + async_desc = bchan->curr_txd;
> +
> + if (async_desc) {
> + async_desc->num_desc -= async_desc->xfer_len;
> + async_desc->curr_desc += async_desc->xfer_len;
> + bchan->curr_txd = NULL;
> +
> + /* manage FIFO */
> + bchan->head += async_desc->xfer_len;
> + bchan->head %= MAX_DESCRIPTORS;
> +
> + /*
> + * if complete, process cookie. Otherwise
> + * push back to front of desc_issued so that
> + * it gets restarted by the tasklet
> + */
> + if (!async_desc->num_desc)
> + vchan_cookie_complete(&async_desc->vd);
> + else
> + list_add(&async_desc->vd.node,
> + &bchan->vc.desc_issued);
> + }
> +
> + spin_unlock_irqrestore(&bchan->vc.lock, flags);
> + }
> + }
This could be written with fewer indents using continue
(and maybe faster using ffs too)
for (i = 0; i < bdev->num_channels; i++) {
struct bam_chan *bchan;
if (!(srcs & BIT(i)))
continue;
bchan = &bdev->channels[i];
/* clear pipe irq */
pipe_stts = readl_relaxed(bdev->regs + BAM_P_IRQ_STTS(i));
writel_relaxed(pipe_stts, bdev->regs + BAM_P_IRQ_CLR(i));
etc...
next prev parent reply other threads:[~2014-03-03 6:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 6:30 [Patch v8 0/2] Add Qualcomm BAM dmaengine driver Andy Gross
2014-03-03 6:30 ` [Patch v8 1/2] dmaengine: qcom_bam_dma: Add device tree binding Andy Gross
2014-03-03 6:30 ` [Patch v8 2/2] dmaengine: add Qualcomm BAM dma driver Andy Gross
2014-03-03 6:49 ` Joe Perches [this message]
2014-03-03 9:38 ` Shevchenko, Andriy
2014-03-07 23:11 ` Andy Gross
2014-03-07 22:29 ` Stanimir Vabanov
2014-03-07 23:07 ` Andy Gross
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=1393829352.13719.73.camel@joe-AO722 \
--to=joe@perches.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).