From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Bresticker Subject: Re: [PATCH V2 2/2] dmaengine: Add driver for IMG MDC Date: Sun, 7 Dec 2014 22:14:05 -0800 Message-ID: References: <1416002384-3525-1-git-send-email-abrestic@chromium.org> <1416002384-3525-3-git-send-email-abrestic@chromium.org> <20141205173553.GS3411@intel.com> <20141207114829.GX3411@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20141207114829.GX3411-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Vinod Koul Cc: Dan Williams , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Grant Likely , James Hartley , James Hogan , Ezequiel Garcia , Damien Horsley , Arnd Bergmann , dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: devicetree@vger.kernel.org On Sun, Dec 7, 2014 at 3:48 AM, Vinod Koul wrote: > On Fri, Dec 05, 2014 at 10:30:53AM -0800, Andrew Bresticker wrote: >> After adding a macro for setting the WIDTH_{R,W} fields it seems fine >> to me. Is there something else you had in mind? > I think whole of this might be a macro :) > > >> > and this depends on dma_slave_config being set, which shouldn't be the case >> > for memcpy > okay looking back yes it depends on bus_width. But how is bus_width set, i > thought the dma_slave_config will set that? The MDC's memory bus width is read from a HW register and set in probe(). -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html