[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D70B786.3010509@st.com>
Date: Fri, 4 Mar 2011 15:27:26 +0530
From: viresh kumar <viresh.kumar@...com>
To: "vinod.koul@...el.com" <vinod.koul@...el.com>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>
Cc: Viresh KUMAR <viresh.kumar@...com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"viresh.linux@...il.com" <viresh.linux@...il.com>,
"jamie@...ieiles.com" <jamie@...ieiles.com>,
Armando VISCONTI <armando.visconti@...com>,
Shiraz HASHIM <shiraz.hashim@...com>,
amitgoel <amit.goel@...com>,
"hans-christian.egtvedt@...el.com" <hans-christian.egtvedt@...el.com>
Subject: Re: [PATCH V2 11/13] dw_dmac: Allow src/dst msize & flow controller
to be configured at runtime
On 03/03/2011 03:47 PM, Viresh KUMAR wrote:
> From: Viresh KUMAR <viresh.kumar@...com>
>
> Msize or Burst Size is peripheral dependent in case of slave_sg transfers, and
> in case of memcpy transfers it is platform dependent. So msize configuration
> must come from platform data.
>
> Also some peripherals (ex: JPEG), need to be flow controller for dma transfers,
> so this information in case of slave_sg transfers must come from platform data.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@...com>
> ---
> drivers/dma/dw_dmac.c | 10 ++++++----
> drivers/dma/dw_dmac_regs.h | 1 +
> include/linux/dw_dmac.h | 30 ++++++++++++++++++++++++++++++
> 3 files changed, 37 insertions(+), 4 deletions(-)
>
Sorry, i missed similar changes for dw_dma_cyclic_prep(). Will resend it.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists