public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	Anmar Oueja <anmar.oueja@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH] dma: ste_dma40: fix up static memcpy event lines
Date: Thu, 23 May 2013 16:02:05 +0530	[thread overview]
Message-ID: <20130523103205.GE30200@intel.com> (raw)
In-Reply-To: <1367610578-2437-1-git-send-email-linus.walleij@stericsson.com>

On Fri, May 03, 2013 at 09:49:38PM +0200, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> The commit
> "dmaengine: ste_dma40: Assign memcpy channels in the driver"
> had two problems:
> - It assigned magic numbers to the memcpy event lines
>   instead of giving them symbolic names.
> - It seems to have missed one of the memcpy event lines,
>   number 51.
> 
> This patch fixes it up.
> 
> Cc: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Vinod: seeking an ACK for this to take it with the rest of
> Lee's patches in a DMA40 branch in ARM SoC.
> ---
Acked-by: Vinod Koul <vinod.koul@intel.com>

Anyone else remaining, if so pls do ping :)

--
~Vinod
>  drivers/dma/ste_dma40.c | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/dma/ste_dma40.c b/drivers/dma/ste_dma40.c
> index 12de79e..cd7b480 100644
> --- a/drivers/dma/ste_dma40.c
> +++ b/drivers/dma/ste_dma40.c
> @@ -56,7 +56,21 @@
>  #define MAX(a, b) (((a) < (b)) ? (b) : (a))
>  
>  /* Reserved event lines for memcpy only. */
> -static int dma40_memcpy_channels[] = { 56, 57, 58, 59, 60 };
> +#define DB8500_DMA_MEMCPY_EV_0	51
> +#define DB8500_DMA_MEMCPY_EV_1	56
> +#define DB8500_DMA_MEMCPY_EV_2	57
> +#define DB8500_DMA_MEMCPY_EV_3	58
> +#define DB8500_DMA_MEMCPY_EV_4	59
> +#define DB8500_DMA_MEMCPY_EV_5	60
> +
> +static int dma40_memcpy_channels[] = {
> +	DB8500_DMA_MEMCPY_EV_0,
> +	DB8500_DMA_MEMCPY_EV_1,
> +	DB8500_DMA_MEMCPY_EV_2,
> +	DB8500_DMA_MEMCPY_EV_3,
> +	DB8500_DMA_MEMCPY_EV_4,
> +	DB8500_DMA_MEMCPY_EV_5,
> +};
>  
>  /**
>   * enum 40_command - The different commands and/or statuses.
> -- 
> 1.7.11.3
> 

      parent reply	other threads:[~2013-05-23 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 19:49 [PATCH] dma: ste_dma40: fix up static memcpy event lines Linus Walleij
2013-05-07  7:31 ` Lee Jones
2013-05-20 12:38 ` Linus Walleij
2013-05-23 10:32 ` Vinod Koul [this message]

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=20130523103205.GE30200@intel.com \
    --to=vinod.koul@intel.com \
    --cc=anmar.oueja@linaro.org \
    --cc=dan.j.williams@intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@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