mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Venkatraman S <svenkatr@ti.com>
To: Anuj Aggarwal <anuj.aggarwal@ti.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SDMA: Fixing bug in omap_dma_set_global_params()
Date: Wed, 23 Sep 2009 13:54:30 +0530	[thread overview]
Message-ID: <618f0c910909230124q773b90f6xd377e67a758e1237@mail.gmail.com> (raw)
In-Reply-To: <1253690346-17865-1-git-send-email-anuj.aggarwal@ti.com>

On Wed, Sep 23, 2009 at 12:49 PM, Anuj Aggarwal <anuj.aggarwal@ti.com> wrote:
> Argument tparams was not being used to program
> global register GCR.HI_THREAD_RESERVED. This patch fixes the same.
>
> Signed-off-by: Anuj Aggarwal <anuj.aggarwal@ti.com>
> ---
>  arch/arm/plat-omap/dma.c |   13 +++++++------
>  1 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/plat-omap/dma.c b/arch/arm/plat-omap/dma.c
> index bf08634..7a7b6df 100644
> --- a/arch/arm/plat-omap/dma.c
> +++ b/arch/arm/plat-omap/dma.c
> @@ -829,10 +829,10 @@ EXPORT_SYMBOL(omap_free_dma);
>  *
>  * @param arb_rate
>  * @param max_fifo_depth
> - * @param tparams - Number of thereads to reserve : DMA_THREAD_RESERVE_NORM
> - *                                                 DMA_THREAD_RESERVE_ONET
> - *                                                 DMA_THREAD_RESERVE_TWOT
> - *                                                 DMA_THREAD_RESERVE_THREET
> + * @param tparams - Number of threads to reserve : DMA_THREAD_RESERVE_NORM
> + *                                                DMA_THREAD_RESERVE_ONET
> + *                                                DMA_THREAD_RESERVE_TWOT
> + *                                                DMA_THREAD_RESERVE_THREET
>  */
>  void
>  omap_dma_set_global_params(int arb_rate, int max_fifo_depth, int tparams)
> @@ -847,8 +847,9 @@ omap_dma_set_global_params(int arb_rate, int max_fifo_depth, int tparams)
>        if (arb_rate == 0)
>                arb_rate = 1;
>
> -       reg = (arb_rate & 0xff) << 16;
> -       reg |= (0xff & max_fifo_depth);
> +       reg = 0xff & max_fifo_depth;
> +       reg |= (0x3 & tparams) << 12;
> +       reg |= (arb_rate & 0xff) << 16;
>
>        dma_write(reg, GCR);
>  }

max_fifo_depth should not be set to zero. Perhaps it deserves a check
similar to arb_rate ?

  reply	other threads:[~2009-09-23  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23  7:19 Anuj Aggarwal
2009-09-23  8:24 ` Venkatraman S [this message]
2009-10-02 21:42   ` Tony Lindgren

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=618f0c910909230124q773b90f6xd377e67a758e1237@mail.gmail.com \
    --to=svenkatr@ti.com \
    --cc=anuj.aggarwal@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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

all inboxes | Powered by JetHome®